Database Develop

Help!! My lock button only unlocks and doesn't lock!

Two days ago, I was running CyanogenMod 5.0.7.1-N1 with the latest version of pershoot's kernel.
I was looking for a replacement launcher app and stumbled across ADW Launcher. I installed it (by flashing the zip file in recovery), but I didn't really like it.
I had no idea how to uninstall it, so I figured I would just flash CyanogenMod again. I did just that, using Clockwork's ROM Manager.
Once I booted back in CyanogenMod, everything seemed normal. I slid the slider to unlock my phone, and everything was fine.
But when I tried to lock my phone, the button wouldn't do anything. I tried literally everything and the phone would not sleep. I restarted my phone, and the VERY FIRST TIME IT STARTS, before you slide the slider to unlock it the first time, the lock button works normally for locking and unlocking. As soon as you slide the slider for the first time and get to the menu, it becomes completely unresponsive.
I have completely wiped my phone, installed the stock 2.1update1 ERE27 ROM, and formatted my SD card, and still it does not work.
On the stock kernel, the screen timeout works fine. After the screen is timed out, the lock button unlocks the phone just fine, and once again, before I slide to get into my phone, the lock button functions normally. It's just as soon as I slide the unlock slider for that first time, the lock button dies.
I have no apps installed expect the ones that came with the stock ROM.
Sorry that was long, thanks for any help!!
tl;dr: Installed ADW launched over CyanogenMod, then uninstalled the launcher and lock button went kaput.

I had the same problem as you before I rooted. The power button would unlock the device and whatnot, but didn't work when trying to put the display to sleep. I sent it in to htc for a warranty repair and all was well until I flashed to cyanogen's 5.0.6 ROM. It stopped working after that, but because it was just fixed, I attributed it to something in the ROM. Once I updated to the latest cyanogen build though, it was working again. So I'd say either try reflashing your current one, or update to a new one and see if that helps.

I've tried reflashing CyanogenMod 5.0.7.1, and there was still the same problem.
So now I'm following the [ROM] Original Shipping Tutorial procedure to get as close to absolute stock as possible.

LOL i had this same problem. But i worked it out.
Try going into spare parts selecting end button behavior and then choosing go to sleep.
I only had this problem with the latest cm rom.
P.S let me know if this helps?

[Q] [RESOLVED] 2 lock screens in TL on JB

Looks like this is by "design". I've observed the issue on other stock ROMs.
Ever since I upgraded my TL30at to at&t-provided JB (9.1.F.1.120) I've been experiencing a strange issue: in addition to my selected lock screen (pattern), I see the JB slide screen with the music player and camera options, too. Specifically: when phone is locked and asleep, I press the power button and see the slide screen for about half a second then the pattern screen appears to unlock the phone; when the screen times out and I press the power button, I see the slide unlock screen (screen and lock time outs are set to different values).
The "main" lock screen has the same background as desktop and the slide lock screen has either the default theme background or the one defined in Settings->Display->Lock Screen.
I also noticed that the option for additional privacy of the lock screen that was present in ICS - blocking the notification area opening unless the device is unlocked - is "missing". I had it enabled. It's not present in JB but the "main" (desired/secure) lock screen behaves as if it is still present and enabled while the swipe screen allows to open the notification area.
I've already tried:
- changing unlock method (the slide screen is always there unless there's no unlock and the lock screen behaves "normally" when it's set to slide);
- resetting the phone (soft and hard resets);
- disabling Nova Launcher.
The device isn't rooted or otherwise modded.
Is this normal behavior in JB or some weird glitch with my install?

sounds weird to me, try a clean install

gregbradley said:
sounds weird to me, try a clean install
Click to expand...
Click to collapse
Noob question (I've dealt only with fully unlocked & rooted devices before): how do I do it?
The install threads I've seen around here are for customs ROMs and unlocked/rooted devices. Did I miss it?

bsined said:
Noob question (I've dealt only with fully unlocked & rooted devices before): how do I do it?
The install threads I've seen around here are for customs ROMs and unlocked/rooted devices. Did I miss it?
Click to expand...
Click to collapse
download pccompanion and run that.

gregbradley said:
download pccompanion and run that.
Click to expand...
Click to collapse
That didn't help. I got 2 lock screens "out of the box". I'll try tomorrow with ADB backup and no PC Companion backup in order to ensure that I get 100% clean JB.
The one thing that keeps on bugging me is that ICS used to have an option for additional privacy of the lock screen - blocking the notification area opening unless the device is unlocked. I had it enabled. It's not present in JB but the "main" (desired/secure) lock screen behaves as if it is still present and enabled while the swipe screen allows to open the notification area.

Re: [Q] [Help] 2 lock screens in TL on JB
Pccompanion will give you a complete pure flash of an out of the box phone as it is Sony's official tool and you download the software straight from Sony.
Have you rooted the phone or done anything else to it
Sent from my star trek communicator
Sony Flagship device circa 2145

Mine does that too. It has done that on every JB rom I have used. I especially notice it now with the AT&T JB. I haven't found a way to get rid of it so I just ignore it.

gregbradley said:
Pccompanion will give you a complete pure flash of an out of the box phone as it is Sony's official tool and you download the software straight from Sony.
Have you rooted the phone or done anything else to it
Sent from my star trek communicator
Sony Flagship device circa 2145
Click to expand...
Click to collapse
I used this repair function to no avail. I also did a full factory reset followed by PC Companion restore also with no luck. The phone isn't rooted. The only customization I made to it outside of standard settings was installing Nova Launcher through the Market.

cjna said:
Mine does that too. It has done that on every JB rom I have used. I especially notice it now with the AT&T JB. I haven't found a way to get rid of it so I just ignore it.
Click to expand...
Click to collapse
I'm a very picky about my UX. The easy workaround is to set timeout and lock to the same value and make power button lock automatically, but that's not how the device was designed to work.

I have tried to no avail to reproduce this bug and no matter which lockscreen i choose in settings I only get the one lockscreen so not sure what else to suggest.

I've now rooted the phone and installed CWM to clean all cache and settings. Nothing helped, so I'm guessing the problem is somewhere in non-user settings and probably has to do with upgrading from ICS. I just wish I could erase the phone like a computer disk and perform a 100% clean install of JB.

bsined said:
I've now rooted the phone and installed CWM to clean all cache and settings. Nothing helped, so I'm guessing the problem is somewhere in non-user settings and probably has to do with upgrading from ICS. I just wish I could erase the phone like a computer disk and perform a 100% clean install of JB.
Click to expand...
Click to collapse
well if you have now rooted you can do a factory reset in recovery and flash another ROM. Make sure you have a .zip for another rom on the sd card first.
Try my stock based custom ROM and see if the problem persists.
PS, if you repair your phone using PCCompanion then that is a 100% clean install from Sony.

Re: [Q] [Help] 2 lock screens in TL on JB
If you're rooted now, uninstall Sony lockscreen, if you don't plan to use it. Pattern lock is AOSP.

[Q] i9000 screen waking itself constantly?!

Recently i put cm11 on my i9000 and now the screen is constantly turning on. As soon as the screen lock is turned on, the phone wakes again.
Sometimes this happens indefinitely and sometimes it only happens once then the screen will sleep after a second press of the lock/power button.
The only consistent thing appears to be that when the lock screen is unlocked the recent apps are always shown.
I've tried formatting/wiping and different night lies and the m4 snapshot but it all happens exactly the same.
Any help would be greatly appreciated.

use this and see if it's the rom or an app that's keeping the phone awake http://forum.xda-developers.com/showthread.php?t=2179651

pryerlee said:
use this and see if it's the rom or an app that's keeping the phone awake http://forum.xda-developers.com/showthread.php?t=2179651
Click to expand...
Click to collapse
Thanks, I've installed this earlier today and I don't quote understand it.
According to wake lock detector, under screen wake lock, running and usage, phone - system (radio) is number one.
Does this mean it's the rom keeping the phone awake?

Not sure how wakelock works to be honest but I don't think it's the rom that's the problem, it sounds like its the radio (modem) try flashing a different baseband for your region and see if that fixes the problem? http://forum.xda-developers.com/showthread.php?t=1870460 http://forum.xda-developers.com/showthread.php?t=1158783

pryerlee said:
Not sure how wakelock works to be honest but I don't think it's the rom that's the problem, it sounds like its the radio (modem) try flashing a different baseband for your region and see if that fixes the problem? http://forum.xda-developers.com/showthread.php?t=1870460 http://forum.xda-developers.com/showthread.php?t=1158783
Click to expand...
Click to collapse
Tried several different radios without any success I'm afraid.
Just tried flashing stock JVU rom and then back to CM11 without any success. Exactly the same issue.
Oddly, if you hold the home key whilst pressing the lock key, the screen turns off and stays off for a while, then wakes after a minute or so again.

New Method
Try going into settings>Applications (or Apps)> Running and check which application(s) is taking up the most memory, it may be that a application from an unknown source is waking up the device, like a virus or your phone is consuming too much RAM. If this is the case try and delete it or run a security scan from the play store such as BitDefender.
Another option is to run a more stable version of CyanogenMod instead of a Nightly, I had problems with Nightly builds and changed back to a stable build. Try the new 4.4 snapshot of CyanogenMod, it is more stable. DOWNLOAD from the official cyanogenmod website, don't update using the option in settings as it always sends my phone into a boot loop. Hope it helps

Try another ROM
Let me know if switching to another ROM helps. I'd suggest Paranoid Android or OmniROM.
The thanks button is right there! just saying...

Gokulbalram said:
Let me know if switching to another ROM helps. I'd suggest Paranoid Android or OmniROM.
The thanks button is right there! just saying...
Click to expand...
Click to collapse
No luck unfortunately, I think I've narrowed it down, and the menu button keeps activating itself.

kcajjones said:
No luck unfortunately, I think I've narrowed it down, and the menu button keeps activating itself.
Click to expand...
Click to collapse
Try Flashing Stock.

Gokulbalram said:
Try Flashing Stock.
Click to expand...
Click to collapse
Stock is doing exactly the same thing

kcajjones said:
Stock is doing exactly the same thing
Click to expand...
Click to collapse
Have you erased each and everything? /data and stuff? also, just see if Touchwake is enabled by any chance

I don't mean to drag this old thread back up, but I've come to use my i9000 again as a backup device and it still has this same problem.
Is there anyway I can prove that it's a button that's faulty (for instance)?
I thought maybe a logger that would show if it detected/logged the home button being pressed when I notice the screen turning itself on, but I can't find such an app.

[Q] Carbon Rom for Xperia ZR

I have flashed the latest Carbom rom for the Xperia ZR but after few minutes screen is not responding that is i am not able to pass the lock screen it was happening even after flashing the older builds can someone please help me to sort this out i have even flashed the correct gapps for the rom.

JellyBeanLover007 said:
I have flashed the latest Carbom rom for the Xperia ZR but after few minutes screen is not responding that is i am not able to pass the lock screen it was happening even after flashing the older builds can someone please help me to sort this out i have even flashed the correct gapps for the rom.
Click to expand...
Click to collapse
disable double tap to wake in display settings

Its already disabled bt still no luck

JellyBeanLover007 said:
Its already disabled bt still no luck
Click to expand...
Click to collapse
make sure u don't have any autokill/fastreboot apps... and make sure u don't swipe away Settings from the task list. if u close Settings the Tap2Wake will reenable. this is a bug in all CM-based roms.

Thankssss i will try that one
but now i got another problem when i am trying to wipe data from cwm its giving me error formating error skip formating likewise

Hey thanks for ur help u were rite it was clean master which was auto killing the settings and so the double tap function was getting started thankssss now every things working fine now
Sent from my Xperia ZR using XDA Free mobile app

If you would still like to use Clean Master, or kill the settings app without any worries, follow these steps.
Clean flash the build you want, preferably latest.
When it boots, do not allow the screen to turn off. This is imprtant!
Go to settings, change all the settings to your preference.
Once you're done, uncheck "Double tap to wake", if you haven't already.
Don't close Settings. Reboot from the power menu.
Done. Screen will not become unresponsive anymore, as long as you do not open the display menu in the settings app. If you do, you will see that the double tap option is disabled. Leave it like that, change the settings you want, then reboot without killing the app.
Bottom line: After doing this, it's perfectly fine if your auto clean app kills Settings, as long as you haven't opened the Display menu.

Cannot unlock screen

Some notifications seem to block unlocking.
It looks like the phone is working fine, I can lock/unlock screen. When it receives a message - it blinks LED. But sometime (one in 10 tries) when I try unlocking it by pressing "power" shortly - nothing happens - the screen remains blank.
If I press "power" quickly multiple times, sometime I can see the lock screen with the clock and notification but just for a fraction of a second. I can still ssh to the phone or "adb shell", it is working. Only reboot helps to unlock the screen.
How to fix that?
Same problem with Moto G (first gen), both are running Cyanogenmod 12.1 nightly (tried many from march till last week).
Thanks!

aikhome said:
Some notifications seem to block unlocking.
It looks like the phone is working fine, I can lock/unlock screen. When it receives a message - it blinks LED. But sometime (one in 10 tries) when I try unlocking it by pressing "power" shortly - nothing happens - the screen remains blank.
If I press "power" quickly multiple times, sometime I can see the lock screen with the clock and notification but just for a fraction of a second. I can still ssh to the phone or "adb shell", it is working. Only reboot helps to unlock the screen.
How to fix that?
Same problem with Moto G (first gen), both are running Cyanogenmod 12.1 nightly (tried many from march till last week).
Thanks!
Click to expand...
Click to collapse
This happens to me when I run a custom kernel, if you changed anything with the kernel revert to stock settings

KuranKaname said:
This happens to me when I run a custom kernel, if you changed anything with the kernel revert to stock settings
Click to expand...
Click to collapse
My kernel came with cyanogenmod image - 3.4.42. Is it "custom" in this context?

aikhome said:
My kernel came with cyanogenmod image - 3.4.42. Is it "custom" in this context?
Click to expand...
Click to collapse
No, it's stock. Did you change any kernel settings?

KuranKaname said:
No, it's stock. Did you change any kernel settings?
Click to expand...
Click to collapse
Since I have no idea how, the answer is "no"

aikhome said:
Since I have no idea how, the answer is "no"
Click to expand...
Click to collapse
Try running another rom and see if it still happens.

KuranKaname said:
Try running another rom and see if it still happens.
Click to expand...
Click to collapse
Every second CM12.1 build I tried since May (or earlier) does this but not every build. I cannot see system here and changelog does not mention ever that this is fixed/addressed.

aikhome said:
Every second CM12.1 build I tried since May (or earlier) does this but not every build. I cannot see system here and changelog does not mention ever that this is fixed/addressed.
Click to expand...
Click to collapse
Try something else from CM12.1, if you are using Moto g 2014 (XT1063/4/8) try this: http://forum.xda-developers.com/moto-g-2014/development/rom-team-radium-1-2-t3170834