Ok so no matter what custom lock screen i seem to use, it works for about 10 mins then my normal lockscreen starts to apply over the custom one even tho just 10 mins before it was disabled. Anyone know how to fix this?
EDIT:
Is this an issue with some apps with the .32 kernal?
Cuz I know that the LED Hack for the N1 isnt working on the .32 kernal.
I have the same issue with the lockscreens and I am till on 2.6.29.6 kernal. I have gone back to using keyguard disabler so I can use trackball to wake the phone. My holster didn't allow the other key to be activated be accident. Use bolter buddy to toggle ringer.
Checkout mylock (beta) on the market.
Are you using taskiller or a similar manager? If so some of them kill all apps on screen lock, which would kill your lock screen, or they kill on time or on autostart, just make sure theyre excluded from anything like that. Im on the .32 kernal and Nexus Torch is working for me so Im not sure about the LED issue.
JoshHart said:
Are you using taskiller or a similar manager? If so some of them kill all apps on screen lock, which would kill your lock screen, or they kill on time or on autostart, just make sure theyre excluded from anything like that. Im on the .32 kernal and Nexus Torch is working for me so Im not sure about the LED issue.
Click to expand...
Click to collapse
Not the camera LED. Its called LED Hack for the n1. It stops the soft keys from staying lit when you have the phone docked.
Reverted back to CM 5.0.3.1 stock.
Lets see if the lock screens work.
Related
I tried several ROMS on my Nexus, but there is a failure on all ROMS with Gingerbread. If the screen remains locked for a few minutes, I can not unlock it (do not turn on) and not let me restart or shut down the phone, I can only remove the battery and wait about 10/20 minutes to the phone automatically restarts.
I happened to CyanogenMod 7 (RC1 and RC2) and LeoGingerBread (both downloaded from this forum)
r0uzic said:
I tried several ROMS on my Nexus, but there is a failure on all ROMS with Gingerbread. If the screen remains locked for a few minutes, I can not unlock it (do not turn on) and not let me restart or shut down the phone, I can only remove the battery and wait about 10/20 minutes to the phone automatically restarts.
I happened to CyanogenMod 7 (RC1 and RC2) and LeoGingerBread (both downloaded from this forum)
Click to expand...
Click to collapse
Try one of the rooted stock ROMS. Make sure to do a complete wipe first.
Rod3 said:
Try one of the rooted stock ROMS. Make sure to do a complete wipe first.
Click to expand...
Click to collapse
Thanks, in a couple of hours notice if I have failed the stock rom
I just tried the stock rom GRI40 and I was not locked, so I guess it will be the kernel in CM7.
Not having that problem at all on stock GRI40; by the way, i'm having an odd issue with GRI40 & Gingerbread. The time to auto-lock the screen uses to change by itself; i think it's on 2' by default, but i changed it to 30' on screen settings and also on Widgetlocker settings...well, once a day, the time changes to 2' again. Anybody else having the same issue? Ideas?
Sounds to me like more of a hardware failure. I have never had any problems unlocking my screen.
This has happened to me a few times.
Possible reasons:
1)bad custom kernel where the buttons dont work. (menu to unlock)
2)bad setcpu setting. i.e. max cpu at 300MHz when the screen is off
3)cpu pegged at 100%, If its at 100% for a certain amount of time the system auto reboots. Happens many a time with CM7 build 14 and words with friends for me.
Make sure u wipe. I've had stock rooted GB and many Cyan nightlys and RC 1&2 and never had this problem. Do you use trackball wake? Configure lockscreen settings in cyan settings. They also use gestures as well if the problem persists. Hopefully one of these options helps u out. BTW I usually wipe everything.
Sent from my Nexus One
Know-Fear said:
Sounds to me like more of a hardware failure. I have never had any problems unlocking my screen.
Click to expand...
Click to collapse
britoso said:
This has happened to me a few times.
Possible reasons:
1)bad custom kernel where the buttons dont work. (menu to unlock)
2)bad setcpu setting. i.e. max cpu at 300MHz when the screen is off
3)cpu pegged at 100%, If its at 100% for a certain amount of time the system auto reboots. Happens many a time with CM7 build 14 and words with friends for me.
Click to expand...
Click to collapse
I doubt it is a hardware failure does not happen to me with Eclair, Froyo or Gingerbread stock, just happened with CM7
Buck Shot said:
Make sure u wipe. I've had stock rooted GB and many Cyan nightlys and RC 1&2 and never had this problem. Do you use trackball wake? Configure lockscreen settings in cyan settings. They also use gestures as well if the problem persists. Hopefully one of these options helps u out. BTW I usually wipe everything.
Sent from my Nexus One
Click to expand...
Click to collapse
I don't use trackball wake, but my nexus is completely blocked, even if I press the unlock button, and I wipe everything before to flash CM7
Guys, im the developer of Power Switch, an app that switches off your tablet's screen when you shut the case.
The main thread can be found here:
http://forum.xda-developers.com/showthread.php?t=1277712
Ive had reports of problems with the folio's light sensor, so would appreciate some debugging feedback.
You can use the lite version to test, it has all the features, but just wont save as much juice.
Thanks in advance. Feel free to reply here or in the main thread, i read both regularly!
Thank you for it.
Are you saying things work properly?
I've played a bit with this app now and I can't get it to work properly.
Here are the two things I've encountered:
1. In the notification bar it says - Power Switch is active, tap here to configure. This doesn't do anything. To open the app/configuration I have to access it from a shortcut or from the app drawer.
2. The light sensor doesn't seem to work. Only response I get from the app is when it's turned up side down. Then it will switch off the screen.
I'm currently running it on FolioMod 1.4
Android 2.2
Kernel 2.6.32.9
What else can I do to help you?
1 - ill fix this, seems to be some sort of funky error
2 - thats sounds like a kernel problem, try using sensorlist app from mareket to check sensor...
Okay, well I think I know why the light sensor is giving us/you such a problem
There is no light sensor
I've seen it being listed in ads and reviews, but mine doesn't seem to have one.
I've got:
* tegra_accelerometer
* AK8975 3-axis Magnetic Field sensor
* AK8975 Orientation sensor
* tegra_tmon
Do you have auto brightness?
No.
I think Auto brightness was available in the Folio3x ROM (Honeycomb) but if it was active and actually working I don't know.
See that means its your rom/ kernel combo thats broken... surely every modern tablet has a light sensor?
I'll give the Honeycomb ROM another go next week and will let you know how it works.
Is anyone else missing a light sensor?
I have taken for granted that this device doesn't feature a light senator... Does anyone have any indication of that there should be one?
Do you have auto-brightness?
I think that we have and I had problem with SOD before I installed this app. Now I only put it in case and after par seconds it turn off screen and when I want to use it I don't have SOD problem. Thank you very much, lite version is OK for me but I'll might buy full version.
Sent from my FolioComb 0.4 using Tapatalk
What is sod?
SOD=Sleep Of Death
That means if you go to hibernation, you can't turn on screen and you must pull out your battery or long press power button(not fo all devices)
Well there apis an auto-shutdown setting...
Well? Any comments?
ftgg99 said:
Well there apis an auto-shutdown setting...
Click to expand...
Click to collapse
as allways. But noone can reproduce SOD - I can't even if I have seen it few times. For me helped long press on power button. Looks like bug in device dependent code - betelgeuse patches for kernel.
I sure can reproduce SOD. More often then not my folio reacts that way. I am currently not turning it of but just dim the screen when I put it away for awhile. Have tried a lot of things but my specimen is "a bit of a bastard". Still I'm hoping someone will come up with a way to circumvent the problem with some software patch. Guess it would have to be done in the kernel...
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.
Hey guys
As most of you probably know, as soon as you select for instance a pin for your lock screen the S4 disables the possibility for lock screen widgets. I'm currently getting around it with xposed and SamsungMultipleWidgets KitKat.
Just curious if there's any way around this limitation without xposed, or maybe even without root? I'm guessing that it's not possible, still.. I'm curious.
Obscure Reference said:
Hey guys
As most of you probably know, as soon as you select for instance a pin for your lock screen the S4 disables the possibility for lock screen widgets. I'm currently getting around it with xposed and SamsungMultipleWidgets KitKat.
Just curious if there's any way around this limitation without xposed, or maybe even without root? I'm guessing that it's not possible, still.. I'm curious.
Click to expand...
Click to collapse
Some ROMs have this feature baked in. SlimKat for instance. I dont believe there is a way whilst using a stock rom without using xposed, at least i never found one, and I looked hard!
fivecheebs said:
Some ROMs have this feature baked in. SlimKat for instance. I dont believe there is a way whilst using a stock rom without using xposed, at least i never found one, and I looked hard!
Click to expand...
Click to collapse
Yeah, I know.. I had it built in while running CM. Just had an urge to go back to stock for a while and was just wondering what features I wanted actually required root (and xposed).
If anyone else knows of a way, please let us know.
Hi gys, slightly different issue here, but would appreciate any help.
basically the PIN lock does not activate until 30 seconds or so after the phone boots up. So there is no securuty on initial boot up.
Its there if I do a reboot. But not there if I do a startup from fully off.
It used to work but at some point a few ROMs ago t stopped working.
I was told it was the kernel but I have tried 4 and all with the same result and have tried several roms.,
Hey guys, Does anyone know how to fix the static screen during the boot animagion and once booted permanently? Its very annoying. I've looked around but can't find anything
Im sorry but you really didnt look... it has been said MANY times that using a custom kernel can fix it. either reStock or werewolf will fix it.
me2151 said:
Im sorry but you really didnt look... it has been said MANY times that using a custom kernel can fix it. either reStock or werewolf will fix it.
Click to expand...
Click to collapse
Neither of them work for me. Its still just static. So yes, I have looked around.
I assume you are rooted, what Rom and kernels are you running? If you have a stock based ROM you need a stock base kernel, werewolf has 2 of each. A werewolf 1.0 albatross.zip and ww 2.0 basilisk.zip for custom based rooms. (lineage-aosp rooms) And the same 2 kernels that have "stock" in the title. For stock based ROMS. Check red dragons kernel thread or try the 1.2 restock kernel. Turn off any screen lock b4 installing the zip in twrp?
I have stock rom and stock kernel.
In the settings, i have second screen to stay on and always show time.
As long as the second screen stays on, the static will not go away.
In my case, second screen stays on, so static does not go away.
What kernel do i need and where ?
tonycstech said:
I have stock rom and stock kernel.
In the settings, i have second screen to stay on and always show time.
As long as the second screen stays on, the static will not go away.
In my case, second screen stays on, so static does not go away.
What kernel do i need and where ?
Click to expand...
Click to collapse
They were mentioned above. You can also cover the proximity sensor and let both screens go off, then it should be fine.
bond32 said:
They were mentioned above. You can also cover the proximity sensor and let both screens go off, then it should be fine.
Click to expand...
Click to collapse
Covering the sensor does not turn of the screen. I dont know why.
Screen turn off ONLY during call, when i get it close to my ear but NOT when i cover it with my hand or flip the phone or what ever else you can think of.