Database Users

Nexus 4 Lockscreen Lag

I've had this issue with lag on the Nexus 4 lockscreen for quite a while.
The problem is that occasionally when I go to the unlock the phone, I press the lock, but the lock will freeze. Sometimes I have to turn the screen off, and turn back on a couple of times before I can unlock the phone.
I've had this issue running CM10.1 and stock rooted android 4.2.2. I've tried doing a complete wipe and re-flashing everything.
Has anyone else had this issue? I've asked a couple of people I know who have Nexus 4's and none of them have had this problem.
Did I do something wrong, is this a common issue, or this an issue with my phone?

nmunro said:
I've had this issue with lag on the Nexus 4 lockscreen for quite a while.
The problem is that occasionally when I go to the unlock the phone, I press the lock, but the lock will freeze. Sometimes I have to turn the screen off, and turn back on a couple of times before I can unlock the phone.
I've had this issue running CM10.1 and stock rooted android 4.2.2. I've tried doing a complete wipe and re-flashing everything.
Has anyone else had this issue? I've asked a couple of people I know who have Nexus 4's and none of them have had this problem.
Did I do something wrong, is this a common issue, or this an issue with my phone?
Click to expand...
Click to collapse
I also get this occasionally from time to time. I honestly have no clue what it could be, since the screen is completely dry as are my fingers when it happens. Its a minor bug so it doesn't bother me that much

brandonc0526 said:
I also get this occasionally from time to time. I honestly have no clue what it could be, since the screen is completely dry as are my fingers when it happens. Its a minor bug so it doesn't bother me that much
Click to expand...
Click to collapse
I also sometimes get lag when I do manage to unlock, scrolling through my screens is very laggy for 5-10 seconds, then it is usually fine.
I have a problem with lockscreen lag on a phone with a quadcore CPU and 2 GB of RAM.

Flash a custom kernel. You'll be less likely to experience lag

Don't get any lockscreen lag on my stock Android.

sigma392 said:
Flash a custom kernel. You'll be less likely to experience lag
Click to expand...
Click to collapse
Have any recommendations?

nmunro said:
Have any recommendations?
Click to expand...
Click to collapse
The latest trinity kernel (125) has perfected the lockscreen lag, It definitely unlocks instantly for me.

username8611 said:
The latest trinity kernel (125) has perfected the lockscreen lag, It definitely unlocks instantly for me.
Click to expand...
Click to collapse
Trying this out now. I especially liked how it told me my system was corrupted once it finished flashing...
First thing I've noticed is that the colour is a lot different. Do I need to play with any settings, or do I only need to have the kernel installed?
Also how often do updates come out?

Messing with the settings is totally up to you. It works great "right out of the box." I don't like the stock color settings, I use trickster mod to change them to rgb 255, 255, 255 and everything else at 0 except saturation and blacks all the way up. This kernel is underclocked to 1026mhz by default, I set it to stock clock speeds. It's also undervolted by default so if you are having stability problems, try bumping up the voltage on all steps by 25mv. Updates come out pretty often, prolly a few times a month.

username8611 said:
Messing with the settings is totally up to you. It works great "right out of the box." I don't like the stock color settings, I use trickster mod to change them to rgb 255, 255, 255 and everything else at 0 except saturation and blacks all the way up. This kernel is underclocked to 1026mhz by default, I set it to stock clock speeds. It's also undervolted by default so if you are having stability problems, try bumping up the voltage on all steps by 25mv. Updates come out pretty often, prolly a few times a month.
Click to expand...
Click to collapse
The colours bothered me so I'm trying the latest franco nightly. It seems to be at the stock clock speed, no weird colours, and it makes the haptic feedback when unlocking feel more like the GNex.

I'm still having this issue with franco kernel. I've been looking around a bit and people seem to say this is related to auto brightness. I'm going to turn auto brightness off for a bit and see if it still happens.
Also, does anyone know if using a 3rd party app for auto brightness would make any difference?

Okay, turns out auto brightness wasn't the issue. Still getting lockscreen lag. Help please.
If I put 5 fingers on the screen (when the screen is off), then press the lock button, when the screen comes on it will be completely unresponsive, some of the time. I'm not always able to replicate this.

for me, some releases of Franco have lockscreen lag, some don`t, try flashing the M2 or other post r121 builds, they are all great performers and maybe you`ll get lucky with one.

if ur using paranoid android, then its a stability issue i guesa cause the same thing used to happen with me...... or else try franco kernel... or update franco kernel if ur using franco, cause an older version had the lockscreen bug, which is now fixed!!!

sigma392 said:
Flash a custom kernel. You'll be less likely to experience lag
Click to expand...
Click to collapse
Flash a stock kernel. You'll be less likely to experience lag

I'm running CM 10.1 and the latest version of franco's kernel.
I've tried using a rooted stock and I had the same issue with lag.
I'm going to try franco's milestone build, see if I still get issues.
Would increasing the minimum clock likely help at all?

I had this problem no matter what custom ROM or kernel I would use I would get this problem I got a replacement phone and don't have this issue anymore
Sent from my Nexus 4

Good Guy Mark said:
I had this problem no matter what custom ROM or kernel I would use I would get this problem I got a replacement phone and don't have this issue anymore
Sent from my Nexus 4
Click to expand...
Click to collapse
I'm thinking this may have been the issue.
How does the replacement process work?
If I save a nandroid backup of my phone, can I just unlock it and restore from there?

Flash the reset kernel from _motley 's kernel thread, it replaces a lot of files that might of got changed via various other kernel flashes with stock ones.
the one that causes a lot of lock screen lag is the /system/lib/hw/power.msm8960.so file
N4_422_stock_kernel_and_components.zip

meangreenie said:
Flash the reset kernel from _motley 's kernel thread, it replaces a lot of files that might of got changed via various other kernel flashes with stock ones.
the one that causes a lot of lock screen lag is the /system/lib/hw/power.msm8960.so file
N4_422_stock_kernel_and_components.zip
Click to expand...
Click to collapse
Can I just flash this with CWM? And then flash back to franco m2?
I actually just got an RMA for my phone, because of this issue and that the back glass panel is a little loose and makes creaking noises. When I send the phone back to google, if I follow all the steps here and lock the bootloader, it should be fine to send back to them?
Google's RMA process was amazing. Took me all of 10 minutes. They're shipping a new one in 3-5 days, and they pay for the return shipping of my old device. The replacement is brand-new, not a refurbished device. My dad's iPhone 4S had a bunch of issues and he would have to book an appointment at the Apple store, which happens to be an hour away, and they would only replace his device with a refurbished one.

[Q] Vibration Intensity Continually Decreases

Hi all,
I have a Galaxy S4 which I have recently flashed CM 10.1 onto, having used another JB custom ROM until then. I have a problem with the vibration. It seems to be working fine after every reboot, but then as I start typing messages and using other functions the intensity of each vibration seems to die a little bit more until it stops vibrating altogether (haptic, notifications, everything). A reboot will cause it to get back to normal again but the same thing seems to happen.
I can't recall if this was happening before first flashing/rooting the phone, so I'm not sure if it's a straight hardware issue. Any pointers?
Thanks

Try going back to stock via Odin and see if it's actually a hardware issue or just CM10.1. Have you tried reflashing CM10.1?

That's a strange issue.
Certain ROMs have "vibration intensity multipliers" as options, e.g. LiquidSmooth and I think ReVolt (both AOKP-based). These are helpful. That might not help you though, given that your vibration's dropping to zero (it won't matter if it's dropping from a higher level in that case).
But to rule out a hardware fault, I'd switch ROMs and see if that fixes the problem. (Because then you'd know it's software-related.)

Te3k said:
That's a strange issue.
Certain ROMs have "vibration intensity multipliers" as options, e.g. LiquidSmooth and I think ReVolt (both AOKP-based). These are helpful. That might not help you though, given that your vibration's dropping to zero (it won't matter if it's dropping from a higher level in that case).
But to rule out a hardware fault, I'd switch ROMs and see if that fixes the problem. (Because then you'd know it's software-related.)
Click to expand...
Click to collapse
emckai said:
Try going back to stock via Odin and see if it's actually a hardware issue or just CM10.1. Have you tried reflashing CM10.1?
Click to expand...
Click to collapse
I'm still new to this so it's a slow and somewhat painful process, but I just reflashed stock today and there doesn't seem to be an issue at all.
I stumbled across this thread where it appears it's a CM10.1 problem. Suggested fix is to disable haptic, reboot, enable haptic. When I get the patience to re-flash and set up my device again I'll give it a shot.

Freeze on charge

I recently rooted and unlocked the bootloader on my Razr M and installed a nightly build of CyanogenMod (I like to live on the edge, I guess.) The first week or so with it was going great, no issues as far as I could tell.
Then I installed a social application that requires GPS location. I noticed that the first time after enabling this the phone would freeze when plugged in to charge. It would freeze to the point where hitting the wake up button wouldn't even activate the screen. Not always, but it has happened on several occasions. So now whenever I charge it (daily), I have to force reboot (hold down Up, Down, Power in that order.) Sometimes it'll even go through the process of "Optimizing Apps" as if they were all just installed.
Firstly, has anyone else experienced this? And if so, is there an "easy" workaround? I can't quite pinpoint how to reproduce the bug, though I've got 3 different Cleaning applications installed that are used daily. That in mind, it's unlikely this is a memory leak bug.
Second, if there's no "easy" workaround, when can one expect the next Stable build of CyanogenMod, if ever? Is it still in development? I see that the last Stable release for this phone was in 2013. It seems like I'll have to downgrade to an earlier build, but just want some input before I do it.
Thanks much in advance

Sounds like an issue with the app, not the ROM. You said yourself that the issues started AFTER installing that app. So, delete that app and report back. Also, a lot of those cleaner apps out there will just bork your phone if you're not careful.
Sent from my Nexus 5

anyone else experiencing freezing lately?

This is my second Ph-1 and it is starting to freeze multiple times a day. I read the previous post regarding Nova causing these issues, I am using the stock browser and so far, so smooth. I really dislike all the "whiteness" of stock and the lack of customization.. but it is worth it for a smooth experience.

twflys said:
This is my second Ph-1 and it is starting to freeze multiple times a day. I read the previous post regarding Nova causing these issues, I am using the stock browser and so far, so smooth. I really dislike all the "whiteness" of stock and the lack of customization.. but it is worth it for a smooth experience.
Click to expand...
Click to collapse
Side loaded any apps?

I've experienced this issue lately. Yes I am using Nova as my daily driver. I just restarted the phone and issue went away. Hopefully it stays away. If it pops up again I'll report back.

I've had my phone for about a month now. I have had Nova loaded since day one but just recently have experienced the freezing and reboots. It is very random for sure. I may try a run without Nova if it happens much more.

Charkatak said:
Side loaded any apps?
Click to expand...
Click to collapse
Nope, nothing sideloaded...

I am using Pixel 2 launcher for over a month and I like it.

I've had crashing on Beta 2 quite a bit with Nova. OTAing to Beta 3 reduces the crashes to once a week using Nova, which is pretty okay.
It's usually when I try to unlock the phone or am in the middle of doing something that everything just times out and reboots :s

Still on nought and have noticed bout the past week or so have had 2 freez ups. I'm using nova also. Rooted with magisk and viper and a batt mod.

twflys said:
This is my second Ph-1 and it is starting to freeze multiple times a day. I read the previous post regarding Nova causing these issues, I am using the stock browser and so far, so smooth. I really dislike all the "whiteness" of stock and the lack of customization.. but it is worth it for a smooth experience.
Click to expand...
Click to collapse
Wow... I've had my Ph1 for over a month, running Nova.(not rooted, don't feel the need to) .. and I've had no issues at all... I'll admit I can recall a few hiccups (nothing major) when I first received it, but after all the updates, mine is running top notch... I understand that this phone had a rough launch... and a butt load of updates... But I honestly can't complain about my experience....

Well I made it almost 8 days this time before it restarted on its own while sitting on my desk. I usually like to reboot my phones every so often but I wanted to see how long it would go this time. DARN lol!!!

qwahchees said:
I've had crashing on Beta 2 quite a bit with Nova. OTAing to Beta 3 reduces the crashes to once a week using Nova, which is pretty okay.
It's usually when I try to unlock the phone or am in the middle of doing something that everything just times out and reboots :s
Click to expand...
Click to collapse
Oreo beta 3 crashing often for me. Nova printer has been my launcher for a long time. Will try to uninstall it and run another launcher to see if that helps.

rootnooby said:
Oreo beta 3 crashing often for me. Nova printer has been my launcher for a long time. Will try to uninstall it and run another launcher to see if that helps.
Click to expand...
Click to collapse
Tried Apex launcher and pixel launcher. No real difference. Phone is difficult to unlock. Takes a long time. System UI crashed. Oreo beta 3 seems overall buggy for me.
Is there a way to troubleshoot whether or not I could be having a hardware issue as opposed to a software issue?

rootnooby said:
Tried Apex launcher and pixel launcher. No real difference. Phone is difficult to unlock. Takes a long time. System UI crashed. Oreo beta 3 seems overall buggy for me.
Is there a way to troubleshoot whether or not I could be having a hardware issue as opposed to a software issue?
Click to expand...
Click to collapse
Have you tried to factory reset and see how it acts? I have had no issues like that with OB3.

Warlord721 said:
Have you tried to factory reset and see how it acts? I have had no issues like that with OB3.
Click to expand...
Click to collapse
I've seen temporary freezes, like a 1-2 second delay but they're pretty rare. Not sure what some others are labeling a freeze. Does that mean 10 seconds, a minute, they need to reboot?

Jank4AU said:
I've seen temporary freezes, like a 1-2 second delay but they're pretty rare. Not sure what some others are labeling a freeze. Does that mean 10 seconds, a minute, they need to reboot?
Click to expand...
Click to collapse
I've tried a factory reset and that didn't seem to resolve the problem at all. In fact, it seems like unlocking got slower after the reset. The only things outside the box I am doing is using the Google camera app, running an app called layout to hide the navigation keys, and running an ADB command that makes the screen slightly larger by moving the top parameters of the screen up closer to the notch at the top of the phone. I guess I can do another factory reset, restore my applications, but don't install Google Camera or make any adjustments to hide navigation keys or change screen size.
I may do that, or just wait for the official release of Oreo which I hope is soon!
If anything here sounds like a hardware issue, I would appreciate your thoughts. Thank you.

rootnooby said:
I've tried a factory reset and that didn't seem to resolve the problem at all. In fact, it seems like unlocking got slower after the reset. The only things outside the box I am doing is using the Google camera app, running an app called layout to hide the navigation keys, and running an ADB command that makes the screen slightly larger by moving the top parameters of the screen up closer to the notch at the top of the phone. I guess I can do another factory reset, restore my applications, but don't install Google Camera or make any adjustments to hide navigation keys or change screen size.
I may do that, or just wait for the official release of Oreo which I hope is soon!
If anything here sounds like a hardware issue, I would appreciate your thoughts. Thank you.
Click to expand...
Click to collapse
But what kind of freezes are you getting? Is it more like brief lag or a complete freeze? If so, what's the duration?

Jank4AU said:
But what kind of freezes are you getting? Is it more like brief lag our a complete freeze? If so, what's the duration?
Click to expand...
Click to collapse
For example, when the phone has been sitting a few minutes I pick it up, touch the fingerprint sensor and get no feedback. The phone seems dead. I push the power button and nothing happens. I can do this several more times and then the phone may, or may not open. When it is working smoothly, I tapped the fingerprint sensor quickly and hear the"click" sound immediately. About 50% of the time this does not happen. If I had to estimate the amount of time it freezes or lags, it is certainly in excess of 10 seconds.
Many times I am forced to hold the power button down until it reboots.
In other cases, I may be in the middle of using the phone, it will start to lag and freeze, and then automatically reboot itself.

rootnooby said:
For example, when the phone has been sitting a few minutes I pick it up, touch the fingerprint sensor and get no feedback. The phone seems dead. I push the power button and nothing happens. I can do this several more times and then the phone may, or may not open. When it is working smoothly, I tapped the fingerprint sensor quickly and hear the"click" sound immediately. About 50% of the time this does not happen. If I had to estimate the amount of time it freezes or lags, it is certainly in excess of 10 seconds.
Many times I am forced to hold the power button down until it reboots.
In other cases, I may be in the middle of using the phone, it will start to lag and freeze, and then automatically reboot itself.
Click to expand...
Click to collapse
I'm on the beta 3 release and I'm not experiencing that at all. Fingerprint unlocks in under 1 seconds almost every time. You may want to try a clean install without your other "enhancements". Personally, I'd do that just to get some stability and/or reliability. That may also save you time once the 8.1 beta drops because if you can determine that's the culprit, you'll know not to install that stuff on the next beta.
Honestly, as finicky as this phone has been for some users, I wouldn't install anything other than normal apps from the Play Store. I'm really holding off on rooting until the 8.1 beta drops so I can still get the ota as soon as it's released. Then I'll start playing with custom ROM's, etc.
I've only had this for about a week, coming from a Pixel. Flashing that phone was the worst experience of my life, looking forward to trying it here.

Jank4AU said:
I'm on the beta 3 release and I'm not experiencing that at all. Fingerprint unlocks in under 1 seconds almost every time. You may want to try a clean install without your other "enhancements". Personally, I'd do that just to get some stability and/or reliability. That may also save you time once the 8.1 beta drops because if you can determine that's the culprit, you'll know not to install that stuff on the next beta.
Honestly, as finicky as this phone has been for some users, I wouldn't install anything other than normal apps from the Play Store. I'm really holding off on rooting until the 8.1 beta drops so I can still get the ota as soon as it's released. Then I'll start playing with custom ROM's, etc.
I've only had this for about a week, coming from a Pixel. Flashing that phone was the worst experience of my life, looking forward to trying it here.
Click to expand...
Click to collapse
Thanks. Good points. I'll take your advice and clean flash.

The phone is less than 6 months old, getting hard freezes. requires restart by holding power and vol down.
Happens almost everyday while watching youtube and trying to switch to any other application.

Random reboot/black screen

Hi all,
Sorry if this has been answered already.
I am currently running no limits on my 6t with the smurf kernel. Everything is running okay but every now and then, i'll try to unlock my phone by switching on the screen and there will just be a black screen.
I have to hold the power button and vol+ key for awhile and it will restart. It has done this 4-5 times this week.
It has not crashed whilst I am using the phone. Only when the phone's screen has been switched off or when its on charge during the night.
I am running 9.0.12 with no limits 5.1
Has anyone else come across something similar or knows what to do to fix this issue?
Any help is appreciated.
Thanks.

This is a mod issue (if I see right, you are on the magisk mod with 9.0.12 OOS, not on no limits ROM), not a phone issue, find the mod's topic and ask there. We all know these risks when we root and use any mods or custom ROMs.
Possible solution: uninstall that mod and check again.
Anyway you are killing your phone with charging overnight, it needs one and a half hour from 0 to 100% battery.

I don't run No Limits, but I did have Smurf kernel for a short while. I would have random device lock ups and it would only happen while on that kernel. Happened to me about three times before I decided to give up and go back to RenderZenith. Ever since switching back to RZ, I've had zero freezes or lock ups.
I'm not trying to bash the kernel, just sharing my experience with it in terms of the issues I had, since they seem to be similar to yours. The kernel otherwise was a beast. Extremely fast and snappy but I couldn't handle those occasional freezes.
Try removing No Limits as the user suggested before me, but the main point of my post is to try reverting to stock or another kernel as well.
Should probably do one thing at a time though, to help determine which was causing the issue.