Beginning with 2.3.4 Launcher Pro, with sporadic frequency, ceases catching the home button presses.
Pressing it during this phase just causes the screen to flicker black.
This has been evident in any ROM I use (Currently Home Base) and this is even the second device I have owned to display this symptom.
If I do a little dance and any combination of resetting its settings, clearing data, clearing defaults, reboots and changing launchers around it will begin to work.
It doesn't usually start during an on state when it's functioning correctly, it begins at boot.
Anyone else experience this?
[Edit] Using an "Extended Controls" widget that includes the auto lock toggle is the cause of that behavior. Toggling on/off the auto lock causes the behavior to cease.
Related
Currently running May 1st Energy ROM, having an issue where regardless what settings I put for battery light settings (2 minute timeout) it always goes back to 10 seconds...any ideas?
Another issue is the problem with the stock lock screen...I want to completely disable it (both slider and soft key screen locks). I was using S2U2 But it causes double slide screen locks...
Hi All,
I have been having trouble with the phone.
The screen has been turning on by itself and not turning off. The screen will not turn off until i hit the power button. It will not turn off until the phone is out of battery.
Is anyone else having this problem?
thanks!
Want to bump this up ... having the same issue. I've uninstalled nearly every app (at least the ones I'd think would be problematic) and it's still happening. I've downloaded Spare Parts today to see if I could figure it out but I don't have enough data yet.
Anyone else have this issue? Even when I press the lock button, I sometimes need to press it multiple times to get the screen to turn off.
I too am having this problem and boy does it suck battery lol
Sent from P3X231
Do you guys have power saving mode enabled or disabled? Just curious, since that's one of the only things (in addition to message notifications) that affects the screen.
can it have anything to do with automatic updates?
i never had this issue. before or after root. i just rooted two days ago
I had this problem before and after root. I also did a factory reset and I thought it was fixed ... but now it's doing it again.
Happens w/ Power Saving mode enabled and disabled.
I've figured out a semi-solution to this which seems to be working:
With Advanced Task Killer:
Enable Auto Kill Frequencey "When screen off"
Set Auto Kill Level to "Aggressive"
Set Security Level to "Medium"
Don't forget to put any apps you don't want killed in the ignore list (like WidgetLocker, your music player, etc.)
This seems to keep the screen locked for me ... but I still can't figure out what app/process is the culprit in waking the screen when it goes to sleep.
I have a Nexus 4 and along with it, a pesky lag problem. My lockscreen consistently freezes when I go to turn on the screen. I'll press the lock button, the screen will come, and then when I press the lock to unlock the phone, it will freeze. I'll have to turn the screen off and then back on again to be able to unlock my phone.
I had CM10.1 on my phone and I thought this was the issue, so now I have a rooted stock, and still have this problem.
Any ideas as to why this is happening?
Do you have Touch Control (app) installed by any chance? It's known for freezing your screen every now and again (on one phone more regularly than others)
If you don't, I haven't heard of random freezes yet, but could be app related.
I have noticed that my back and recents buttons seem to have stopped working. I had them set so that they were always lit up but they've disappeared.
Has this happened to anyone else and did you manage to fix it? I've looked through the settings and can't see that I've changed anything.
Currently running Action Launcher.
I have noticed that if I touch the Home button briefly, when using the Sense launcher, two small symbols appear briefly - a "b" and something else... Have I accidentally engaged some accessibility feature unwittingly?
ETA: I properly switched it off and restarted it, and the buttons reappeared, lit up as expected. It was a bit of a worry though. Hopefully this will not reoccur.
Hello,
There is this weird problem that came out of nowhere. I usually sleep listening to music and sometimes I weak up with the phone battery completely drained so I have to charge it. Today after charging the phone some parts of the system lost their functions. These are the problems I discovered so far;
-The home(LeEco) and the multitask buttons are not doing their main functions even though the phone registers the touch inputs from the buttons and they light up. The home button can even lock the phone on long press but won't take me to the home screen.
-I have the swipe shortcuts button enabled but it won't take me to home screen or multitask screen. The "go back" option, however, is still working along with the back button. I can go to the home screen by swiping or exiting apps with "go back" button.
-I can't download apps from google play store even on wifi with auto-update enabled. it's stuck on download pending.
-I can't open the notifications management from notifications.
-Connecting the phone to my PC does not show connection options.
-Screenshot doesn't appear in the notifications. The notification area remains empty.
So far these are the ones I discovered. Do you have any idea what causes that and how to fix it? I didn't do a factory reset yet as I can't transfer the data to my PC. Eui 5.9.026S I haven't had any of these problems up until this morning.
Thanks in advance.
Backed up data using an app and factory reset solved the problem.
The actual problem seemed to be:
1-The multitask screen virtually opens but it appears behind the background aka it doesn't actually appear. I think because whatever app that is responsible for it does not have the draw over other apps permission(?).
2-The notifications are there but does not appear in the notifications bar menu. I made sure by using the a notification history app. So it might be notification access permission problem(?).