Related
What am I doin wrong ? Time out is set at 15 sec.
EDIT: Solved by using different SMS app. Email app works fine
nope.....email works, sms works, not missed call keeps phone awake all the time....
am i the only one ?
I had this problem... Had to reboot the phone.
I have noticed times when my screen was on. When I tried to determine why it seemed that I had received a mms over two minutes prior. My screen timeout is thirty seconds. I have since rebooted and will see if it makes a difference.
Sent from my SGH-T959 using XDA App
I've rebooted numerous times since I've gotten the phone. I prefer the stock messaging app and don't want to *have to* use something else to make it work right.
Any other ideas?
Looks like this is one of the bugs on the phone.....
Thank god all bugs are software related so far. With nexus it wad mostly hardware/software things
I think I figured it out (at least for me)...
I disabled the "puzzle lock" thinking it would be a pain in the neck when trying to unlock the screen. Come to find out, disabling it is what is leaving the display on when receiving a text. Enabled the puzzle lock, and the display comes on for a sec or two and then shuts off when I get a message.
I prefer very few steps to get where I wanna go. I don't like passwords or codes when unlocking my screen so I disabled it. Either way, though, I have swype the screen to unlock it so it's not a big deal to have the puzzle lock on...
Since 1.8.3 I have noticed 2 very annoying issues:
1: Several times a day, my Atrix will stop detecting a finger swipe. No error, just no response. I must reboot to regain finger scanning.
1: Screen Timeout: The screen will frequently, but not consistently go off after only a couple seconds of idle time. It doesn't dim first and if you hit the power button it comes back to the screen you were on, not the lock screen.
Both of these issues happened with vanilla 1.8.3 and with Gingerblur and NEVER before the update.
Anyone else?
Fingerpring issue for me as well but also the button sometimes wont put my phone in sleep and ill have to pull battery cause its unresponsive but never the screen issue you're having. This update is full of bugs they need another update fast just to fix what this one broke. Oh and I think about 90% of people that updated have reported an issue with the fingerprint scanner
But thats just my 2 cents
Sent from my Atrix
If both of these issues are known and have been reported, feel free to lock or delete. I searched and didn't find any thread titles about this, but did not read every 1.8.3 thread.
I met the fingerprint issue too after 1.8.3 upgrade
Sent from my MB860 using Tapatalk
i had fingerprint sensor issues too, when i had stored fingerprints and restored settings for fingerprint sensor using Titanium backup. A wipe data may solve this(int titanium backup).
in 183 there is a new setting in Location And Security!
The phone is not necessary anymore to lock, when the screen goes off.
the screen can go off in 5 mins(in display settings)
and the mobile can locked in 10 mins(in location and security)!
i like this setting!
Paschalis said:
i had fingerprint sensor issues too, when i had stored fingerprints and restored settings for fingerprint sensor using Titanium backup. A wipe data may solve this(int titanium backup).
in 183 there is a new setting in Location And Security!
The phone is not necessary anymore to lock, when the screen goes off.
the screen can go off in 5 mins(in display settings)
and the mobile can locked in 10 mins(in location and security)!
i like this setting!
Click to expand...
Click to collapse
Where is the new setting in "Location and Security", I am not finding it. Thanks
charlyee said:
Where is the new setting in "Location and Security", I am not finding it.
Click to expand...
Click to collapse
I don't see it either in 1.8.3. The item "Security lock timer" that would be used for this is disabled (grayed out).
fingerprint issue here too just experienced for the first time yesterday.
i swipe it and there is no response.
good that there is a list of people here with the same issue so motorola can acknowledge it as a legitimate bug and hopefully fix it
Can someone else verify this? When I change the screen timeout from 15 to 30 seconds, then reboot the phone, it switches back to 15 seconds.
wookiebush said:
Can someone else verify this? When I change the screen timeout from 15 to 30 seconds, then reboot the phone, it switches back to 15 seconds.
Click to expand...
Click to collapse
this sounds like the GingerBlur 3.0 bug...upgrading to 3.1 fixed this for me
I am having issues with WidgetLocker and the fingerprint recognition, has anyone else experienced this issue with WidgetLocker? I have been having no issues, with the fingerprint scanning, once I turned off WidgetLocker.
Yes.
You are right!
I now recorded again fingprnts and that setting grayed out!!
I didn't used fingerprints cs some probs I had after restoring settings from backups, and waited to have 183 with 3.0 gingerblur..
Sent from my MB860 using XDA App
I found that powering off the device, pulling the battery for a few minutes, re-installing the battery, turning the Atrix back on, then wiping and re-doing the fingerprints permanently fixed my issue.
This issue is not the same issue as when TiBu backs up fingerprint data. This is an issue with the scanner being none responsive. OP this issue has bot be talked about here but on the Moto forums it's been reported by many users.
But thats just my 2 cents
Sent from my Atrix
I also had my first fingerprint issue since owning this phone for the first time yesterday after getting 183. Never had it ever before...somethings wrong with this update if multiple people are getting it for the first time now.
David
lanyao1920 said:
I met the fingerprint issue too after 1.8.3 upgrade
Click to expand...
Click to collapse
add me to the bad fingerprint group
Same issue with Widget Locker. Sometimes when I hit power, I can swipe finger and all is good. Other times, swipe does nothing - I have to slide the screen lock, then I can swipe (or enter PIN).
Can't seem to find any pattern to when it works or doesn't, but it does do this pretty often. Good thing is, it doesn't completely lock up - if I don't get the double-vibrate for a bad finger swipe, I know that I need to do the screen slider first.
Just to add to the people on the list, I experienced the fingerprint issue once, hasn't happened since though
the best thing to do is actually complain on the motorola support forum ...
i already did
https://supportforums.motorola.com/thread/50138?tstart=0
moto engineers actually look at that forum ...
So I read this thread and thought to myself, "Self, Thank G-d you don't have this problem." And then, of course, I jinxed myself. Add me to the fingerprint issues list!!
I did a power-off, battery remove, battery install, power-on, remove fingerprint data, reboot, then redo fingerprint calibration. If you don't hear back from me, assume it resolved the issue....otherwise, I'll report back....
How absurd?!
--Q
My friend just got a G2 and is having this issue as well. I use a pattern unlock and am running Clean Rom. Some times when I try to unlock the screen it just randomly shuts the screen off while Im trying to draw the unlock pattern. I'm hoping someone has a solution for this.
Thanks
prerunnerseth said:
My friend just got a G2 and is having this issue as well. I use a pattern unlock and am running Clean Rom. Some times when I try to unlock the screen it just randomly shuts the screen off while Im trying to draw the unlock pattern. I'm hoping someone has a solution for this.
Thanks
Click to expand...
Click to collapse
When I use the power button on the back of the phone instead of the knock-on, I had this same problem. I was rooted but on stock rom. I've read other posts about the same problem. I would try to put in my pattern and midway through the screen turns off. Sometimes it would be two seconds, sometimes like 10. Don't know what the problem was.
My knock-on feature was barely working. Some guy recommended getting this case: http://www.amazon.com/gp/product/B00FEQU1NG/ref=oh_details_o01_s00_i00?ie=UTF8&psc=1
I needed one anyway so I got it. Haven't had an issue with the knock-on feature anymore. No idea why haha but whatever, it works. Kind of a ghetto workaround.
I'm having the exact same issue.
Factory reset several times, installing my usual apps or having just the default apps without updating them didn't make any difference.
After a factory reset I disabled the knock knock feature and still, when I try to bring my screen up and unlock, it immediately shuts off, preventing me from swiping.
Another side effect is, when I make a phone call, the screen immediately goes blank and it will never turn back on unless I restart by holding on to the power button, this is especially inconvenient when I need to dial some options (i.e.) voice mail options, corporate automated options.
All of the above happened while I had my Incipio feather shine case. (incipio.com/cases/smartphone-cases/lg-smartphone-cases/lg-g2-cases/lg-g2-cases-verizon/feather-shine-case-for-lg-g2-verizon.html) I took the case off and did another factory reset last night, and so far the knock-on rate has improved from 0% to at least 60-70%... Strangest thing.... If anyone else can shed some light onto what the hell happened/is happening, I'd really appreciate it! It's been a frustrating ride since this problem surfaced about a couple weeks ago. I had this phone for about 2 months now....
I'm having this problem too. It happens with both knock on and power button wake. I have noticed that the screen is not actually immediately turning off, though. In a completely dark room, I can still see faint outlines of my lock screen. Then, after the brief time out for dimming, the screen will go to its dimmed brightness (which is far brighter than what's concurring after waking the phone). I'm able to unlock, reboot, and usually that will solve the problem for a little while, but this is getting frustrating.
Stock rom, rooted, TWRP, Nova Launcher, and xposed. I'm not sure what's causing this.
I know it's been said many times but if you block the sensors with your fingers after waking the device, your screen will turn back off. Its a security feature/bug and I would assume this is what's happening here.
I ended up getting a certified-like new replacement from verizon... While I had the old one, I did a test with that sensor you're talking about and it didn't really make a difference. I made sure the sensor area was clean without anything covering it and the problems persisted. I really hope LG can find the root cause of this and fix it... Very frustrating.
Not a bug. But this is a feature we do not want. It is called proximity sensor. It is sensing too far imo. It is actually the one next to the front cam. Dont block it within 5 inches in front or you phone will sleep again. That should work with flip case. Annoyingfunction imo. Your device is not broken.
yonba said:
Not a bug. But this is a feature we do not want. It is called proximity sensor. It is sensing too far imo. It is actually the one next to the front cam. Dont block it within 5 inches in front or you phone will sleep again. That should work with flip case. Annoyingfunction imo. Your device is not broken.
Click to expand...
Click to collapse
exactly. the sensor in very sensitive to being covered. Because its hypersensitive and having undesireable effects I would consider this a bug since it is buggy.
I figured out what the issue was, at least on my phone.
Lightflow was detecting a bunch of alternate LEDs, which I felt inclined to tick the check boxes for, just to make sure it could control the LED fully. Having those boxes checked caused my phone to do this. Everything is fine since I've unchecked them, though. No sensor issue, no proximity/case issue, just Lightflow (which still works without those alternate LEDs checked).
Having this issue with my G2, its very annoying. Knock on does not work and screen shuts off after about half a second that I press the power button. Had to reflash to stock the first time this happened and fixed it but after about a month the same problem occured. I could however open by pressing one of the volume button together with the power button.
Hoping to find permanent fix for this problem.
thirtynation said:
I figured out what the issue was, at least on my phone.
Lightflow was detecting a bunch of alternate LEDs, which I felt inclined to tick the check boxes for, just to make sure it could control the LED fully. Having those boxes checked caused my phone to do this. Everything is fine since I've unchecked them, though. No sensor issue, no proximity/case issue, just Lightflow (which still works without those alternate LEDs checked).
Click to expand...
Click to collapse
Yeah that's it Lightflow
Disabling all the additional led found resolve my problem
THX
bigiuly said:
Yeah that's it Lightflow
Disabling all the additional led found resolve my problem
THX
Click to expand...
Click to collapse
Please tell me where to find these settings
taqikazmi said:
Please tell me where to find these settings
Click to expand...
Click to collapse
Settings / Led Control
bigiuly said:
Settings / Led Control
Click to expand...
Click to collapse
There is no option in settings like LED.
taqikazmi said:
There is no option in settings like LED.
Click to expand...
Click to collapse
In settings of Lightflow app
bigiuly said:
In settings of Lightflow app
Click to expand...
Click to collapse
I installed the app and fund the settings but all of them are already unchecked
I cannot find a solution for this but the issue is when I miss a phone call when the phone is in my pocket, it automatically unlocks, and drains my battery.
I'm running 4.4.2 rooted on my AT&T Moto X, and I thought 4.4.2 would fix it. I do not have a screen lock
Any help is appreciated.
Thanks!
97vulcan said:
I cannot find a solution for this but the issue is when I miss a phone call when the phone is in my pocket, it automatically unlocks, and drains my battery.
I'm running 4.4.2 rooted on my AT&T Moto X, and I thought 4.4.2 would fix it. I do not have a screen lock
Any help is appreciated.
Thanks!
Click to expand...
Click to collapse
Hmm sounds like a strange issue...
You mean you don't have a screen pin/code/password, or that you don't have even the sliding unlock button?
Have a look in Settings > Display
What timeout do you have listed under sleep? The default is 30seconds, but it goes all the way up to 30min (which I would expect could definitely drain some battery...
Let us know and we may be able to help you further...
samwathegreat said:
Hmm sounds like a strange issue...
You mean you don't have a screen pin/code/password, or that you don't have even the sliding unlock button?
Have a look in Settings > Display
What timeout do you have listed under sleep? The default is 30seconds, but it goes all the way up to 30min (which I would expect could definitely drain some battery...
Let us know and we may be able to help you further...
Click to expand...
Click to collapse
I do not have a password lock on my phone, Just the active display slide to unlock the phone. When a call comes in, I get the display to answer or ignore, but if I leave it go, it will just unlock to the home screen, then after a short time, the screen will shut off.
Thanks!
97vulcan said:
I do not have a password lock on my phone, Just the active display slide to unlock the phone. When a call comes in, I get the display to answer or ignore, but if I leave it go, it will just unlock to the home screen, then after a short time, the screen will shut off.
Thanks!
Click to expand...
Click to collapse
Ok, that is definitely not normal. Are you BL unlocked, or are you using the Pie root exploit? Or Safestrap?
I would suggest flashing the entire 4.4.2 AT&T SBF file using the manual method as described in the Return to Stock thread:
DO NOT DO THIS IF YOU ARE USING SAFESTRAP
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
You will download the 4.4.2 AT&T SBF file from here: http://sbf.droid-developers.org/phone.php?device=0
As I seem to be telling people often, the only way to fix a corrupted filesystem (OR modifications made by previous exploits like Pwn/SlapMyMoto and MotoWpNoMo) is to flash the entire SBF file. Performing a "factory reset" cannot repair a damaged filesystem.
Often, it will fix ALL of your problems.
Good Luck
Did you install any apps, that plays with those settings after rooting?
thanks for the replies guys...I don't think so on the apps after root. IIRC, it did this before rooting the phone, so I thought it was a 4.4 issue.
it will unlock to the home page after every call, unless I answer, or ignore the call.
I'm using Xposed with these modules:
App Settings
GravityBox
HideCarrierMotoX
MinMinGuard
SoftkeysFadeMod
Twisty Switch
Xblast Tools
XPrivacy.
Again, I do not have a lock screen..when I try to enable one it does something funky with my electronic buttons, even after reboot. Not sure if it's because of SoftKeysFadeMod, or what..
I'm surprised others have not had this issue.
Thanks for you help.
97vulcan said:
I do not have a password lock on my phone, Just the active display slide to unlock the phone. When a call comes in, I get the display to answer or ignore, but if I leave it go, it will just unlock to the home screen, then after a short time, the screen will shut off.
Thanks!
Click to expand...
Click to collapse
May I ask if I understand correctly? You have no security setting, only active display enabled. If this is the case, this seems like normal behavior.
You screen turns on when you get a call, you don't answer. Until the screen time out kicks in, you see your home screen.
Once it goes dark, you should have an active display notification.
What Am i missing or what behavior are you expecting?
rtm1102 said:
May I ask if I understand correctly? You have no security setting, only active display enabled. If this is the case, this seems like normal behavior.
You screen turns on when you get a call, you don't answer. Until the screen time out kicks in, you see your home screen.
Once it goes dark, you should have an active display notification.
What Am i missing or what behavior are you expecting?
Click to expand...
Click to collapse
you pretty much hit it on the head...I was hoping the phone's display would not unlock to my desktop if I miss a call, but rather show the missed call on the active display.
I'm going to enable a security setting, and see if this changes the outcome.
Thanks
After enabling the swipe to unlock, I no longer have an issue with my phone unlocking when I miss a call. That seems to be the solution.
Thanks for your help
So for the last couple of days my HTC One M7 would recieve a notification and the screen would just stay on the entire time for no apparent reason. Im on latest OmniROM and its starting to bug me. Like for instance I get new mail on Gmail in the middle of the night. The screen turns on, it show the notification, and it doesnt turn off until I turn it off. If I restart, its fine for a few hours, but as soon as I get a notification, the problem reappears.
Nobody, seriously?
Sinistersky said:
Nobody, seriously?
Click to expand...
Click to collapse
Dude, you took less than 24 hours before bumping. Not everyone checks the forums regularly.
Also, per the FAQ, bug reports belong on jira.omnirom.org
However the behavior you describe is a feature in Omni. Let me guess - you turned on Active Display and forgot about it? (Since it's off by default, and the behavior you describe is not something I've ever seen on any device when AD was disabled.)
Entropy512 said:
Dude, you took less than 24 hours before bumping. Not everyone checks the forums regularly.
Also, per the FAQ, bug reports belong on jira.omnirom.org
However the behavior you describe is a feature in Omni. Let me guess - you turned on Active Display and forgot about it? (Since it's off by default, and the behavior you describe is not something I've ever seen on any device when AD was disabled.)
Click to expand...
Click to collapse
Nope.
Just to note, I am seeing the same thing on my nexus 5 running the 10/13 nightly. AD is disabled and I have never enabled it. I was wondering why sometimes I would pull my phone out of my pocket and the display would be on. Since reading this I have verified that this happens when I get a notification. I will submit a bug report on jira.omnirom.org.
eta: oops, I just realized you need an account for jira.omnirom.org.
VFO said:
Just to note, I am seeing the same thing on my nexus 5 running the 10/13 nightly. AD is disabled and I have never enabled it. I was wondering why sometimes I would pull my phone out of my pocket and the display would be on. Since reading this I have verified that this happens when I get a notification. I will submit a bug report on jira.omnirom.org.
eta: oops, I just realized you need an account for jira.omnirom.org.
Click to expand...
Click to collapse
This doesn't occur on any of my devices, including a Nexus 5.
Are you running some sort of notification customization app of some sort?
Define "screen on" - Lockscreen? Blank with backlight on?
Entropy512 said:
This doesn't occur on any of my devices, including a Nexus 5.
Are you running some sort of notification customization app of some sort?
Define "screen on" - Lockscreen? Blank with backlight on?
Click to expand...
Click to collapse
I am not running any notification customization apps just straight Omni nightlies. It happens with any notification that I receive. It goes to the lock screen and stays on until I unlock it. I am going to wipe and reinstall the ROM and try and determine if it's an app issue.
VFO said:
I am not running any notification customization apps just straight Omni nightlies. It happens with any notification that I receive. It goes to the lock screen and stays on until I unlock it. I am going to wipe and reinstall the ROM and try and determine if it's an app issue.
Click to expand...
Click to collapse
Do you have "screen stays on while charging" enabled? Even then, it shouldn't be turning on for a notification in the first place.
None of my devices turn on for a notification in any situation, and the screen always shuts off quickly (faster than the screen timeout setting) when it's at the lock screen unless "screen stays on when charging" is set in Developer Options.