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] Disable/Remove SafeMode

I recently observed, that my N1 doesn't want to reboot normally. It has basically the same symptomatic than described in this Thread. HBoot is unresponsive since I press the Trackball, reboots only back to HBoot/SafeMode, but in SaveMode everything behaves as expected. the Commands ADB and fastboot are fully functional and I can flash even Roms. The "Workaround" described in that Thread - to trigger and move the trackball - has helped once only, but seems broken now.
To kind of "fix" it I'm thinking of the possibility to REMOVE that SafeMode completely from the Rom. Does anyone know, if this is possible at all? The Rom doesn't matter, and if I have to compile AOSP or Cyanogen or whatever, I'll do whatever needs to get done. Maybe I can just change the behavior from that "SafeMode" in the assumtion, that it is a tiny simple script that justs prevents loading of Apps.
So I basically want to get confirmed, if you think that this is possibnle at all. On top of that, it will be very kind, if someone has some additional hints for me.
Thank you in advance for any response

No lock screen when pressing power button, but do have power/shut down menu?

Hey guys n girls,
Basically my S3 doesn't sleep anymore the screen stays on 24/7? I can't lock the screen using the power button and it doesn't even lock it's self? Even timed lock doesn't work it just stays lit all the time. It's really annoying when I need to sleep at night too plus it chews the battery and will run out before morning so I have to put it on charge when it doesn't need to be charging.
I've wiped and done a factory reset and it does nothing to fix the issue. I've reinstalled fresh both 4.4.4 and 4.4.2 and both still have this issue? I'm about to flash back to 4.3 or even 4.1.2 if I have to.
Yes I've checked the file inside /efs/imei and it has the text "No" which I believe has been the fix for most other people with similar issues? However one striking difference between my issue and most others I've read on XDA from various Samsung devices is this: I still have access to my power menu and my phone doesn't look to be in safe mode?
Any help would be greatly appreciated. Thanks
Sent from my chalk and slate

I think is a hardware related issues. Have you tried taken the battery out? This probably won't do a thing but would not hurt to do so.
Also update your software using KIES just reset using it too.
Hope it helps...

Cheers bud. I have been around here for quite sometime now (no spring n00b is what I am saying) but cheers for your response.
For anyone suffering the same fate....I couldn't find a solution so I pretty much did:
1).a nandroid backup;
2).then titanium backup (just incase and for when I restore later on);
3).I then wiped via recovery;
4).then flashed 4.1.1 stock via Odin;
5).flashed recovery via Odin;
6).rebooted into stock ROM; checked that I DID in fact have lock lock via power button (which I did - as I thought);
7).flashed 4.4.2 via CWM zip in recovery;
8).signed into accounts (*unchecked restore data* THIS IS A BIG MUST! If you are new here make sure that no old data is interferring Google sets the checkbox to restore previous data by default - NOTE: Put your phone into airplane mode ASAP after first boot and signing into your Google account, uncheck sync which is ALSO set by default, then uncheck restore application data).
9).restored via titanium backup (only restored the absolute necessary i.e. text messages, calls and contacts);
10).Go through the tiresome restoration process via Titanium backup (invest in Pro if you have to - it's certainly worth while!)
Now enjoying fresh working firmware with power button locking the lock screen as it should. Have no idea what caused it and I guess I will never know? All I know is that it wasn't the usual suspects when it came to my issue (it never is actually)

Nexus 6 touchscreen issue

The touchscreen does not work after the lock screen, if you restart the phone, the sensor starts to work again, but once again no longer lock. I tried a lot of firmware, such as android n and m stock, aospa, pure nexus. The problem is solved, if you put a custom kernel, but if you disable the settings core gestures (for example wake2sleep on elementalx kernel), then the problem returns. Sensor itself works well, but before the block a screen. What to do? I can not understand what the problem is. I think is not a hardware problem, because touchscreen working nice.

Android touchscreen doesn't work on twrp recovery(any version)

I don't understand what the problem is either. Can you please try explaining it again?

dahawthorne said:
I don't understand what the problem is either. Can you please try explaining it again?
Click to expand...
Click to collapse
Touch screen dont work, if i lock the screen after rebooting (by power button). If i rebooting phone, touch will work, but if i again lock phone by power button, touch screen again dont work. This problem in all roms, and if i flash custom kernel, problem disappears. Sorry for my english.

Expanded FIX for Touch / Calibration Screen Issues

My Touch Screen DiED!!! (A Sad Story that Ends Happily)
I have flashed many a rom on my N910T Note 4. But yesterday I thought I'd update my TWRP install, and elected to use the new TWRP app to do so. Right TWRP file (double-checked). Fired up the app... and apparent success. On reboot, however, what looked to be
*DISASTER*
I touched my screen but nothing happened. Then I moved my finger and something elsewhere than under it opened up. In short, the sensors had become non-calibrated - they no longer properly detected where on the screen I was touching. The fact they did at all was better than nothing... but not much.
First, then, I did at least have some ability to still do things.
Second, better, I found that the s-pen's sensors worked just fine! Boy, was that helpful when it came to trying to type in my pin number / password.
Third, initial looks on the ol' google revealed people saying I'd have to buy a new sensor for the touch screen. Arrrgh!!
BUT THEN THE GOOD NEWS... I HOPED!
I discovered a number of folks suggesting what sounded almost James Bond-ish... a code, input into the phone touchpad, that when "called" could result in a calibration reset. Over and over again, there it was:
=================================
"dial *#2663# and update the touch FW by pressing TSP FW update (General)"
=================================
Okay, said I. Tried it from my new TWIZd rom. But no love. I got an error message. But then it occurred to me to read the many posts on this code more carefully... and sure enough, they did suggest that using the OFFICIAL rom provided by Samsung/my provider was necessary. Sigh... that meant navigating TWRP -- which by the way was also affected by the bad calibration. It was doable... just... by figuring out where my touches were actually activating the screen (it was less severely affected at the top but very severe near the bottom). Eventually got the phone wiped (Thank God I had just backed up my sweet TWIZd install to the ext sd card!). Luckily, I had a generic old copy of my phone's original rom on the ext sd, though it was one that had been debloated and rooted. I hoped it would work....
The flash hung. Forever. heading for 20 minutes. Finally I pulled the battery, not hopeful, and restarted the phone. *WHEW* it came up with the rom installed. Skipping both google and samsung installs, I went right to the Home screen and used my s-pen to type in the code then hit the call key.
Up came a screen of buttons, including a greyish TSP FW update (General) button. (See pics; neither is a Note 4 but both give accurate idea of what the screen looks like when the code given above is dialed in and works correctly.)
I tapped it with the s-pen.... and my screen was fixed!!
I made sure to use TWRP to backup that generic rom to my 128g external sd card - that way if this happens again I can "restore" it via TWRP and repair the phone quickly.
One thing is for certain... I sure appreciate this community of folks, which is where I found much of the info. And I will not be using that TWRP app (created by commercial interests anyway) again. Back to installing TWRP the old way, via either a *.tar TWRP file and ODIN via a PC or via flashing an *.img file w/ TWRP itself.
That's my story and I'm sticking to it.
Hit thanks if you found this amusing / helpful / or just plain odd.

Hi,
SO...I am pretty much in the same boat you were... but I have not been able to get the dialer thing to work...
when I type it in, it just flashes something to fast to see.. and then says "MMI complete" .
So far the ONLY thing I have done with this phone is root it (using Odin and chainfire) ... and install the wrong TWRP ... and then install the correct TWRP.
As far as I know, I still have the original ROM on it! I had not gotten to the point putting a rom on!!
Any suggestions?
Thank you for any help...

Thanks Shonkin, this worked for me on my SGN4, after flashing the bootrom with a Vodafone stock image.
Much appreciated