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
Related
I used the update.zip from the Samsung site to update to EB13, everything went off just fine except my Epic now takes an average of 2 seconds to wake from sleep after pressing the power button, sometimes going up to 4 or 5. Not the worst thing in the world, but pretty annoying.
I narrowed it down to my non-usage of the lock screen. I typically run without using a lock screen at all (disabled via SwitchPro Widget). If I turn the lock screen back ON, my Epic wakes from sleep either instantly or within 1/2 a second. With the lock screen disabled (no pattern lock either), it's super slow to wake.
Anyone have any ideas on what I could try?
Mine works just fine, but I'm using the lock screen, try uninstalling that widget and see if it corrects the problem when you use the lock screen.
Small update to this. I had an idea to move all the apps that I had moved to the SD card back to the phone to see if that helped. It does. With the lock screen on, my Epic comes back from sleep instantly every time. With lock screen off it varies between 1/2 and 1 second.
The apps I moved to SD were ones I hardly used.. I don't know why that would have an effect on the wake time?
Mine seems a bit slow too. But it's not the 4 or 5 seconds you described. It seems like it's about one second, when it used to be anywhere between instantly and half a second.
It's kind of annoying because the delay is just barely too long to where I start second guessing myself on whether or not I pushed the button in all the way or not.
Go to your display setting and reset your horizantal calibration accelerometer... that fixed my phone waking up issue...
Sent from my SPH-D700 using XDA App
Unfortunately, I had already tried recalibrating. I do, however, have no lock on and widget locker running. Do any of you use either of these?
toxicsociety said:
Unfortunately, I had already tried recalibrating. I do, however, have no lock on and widget locker running. Do any of you use either of these?
Click to expand...
Click to collapse
I use the same program as you do and I have the exact same problem So your not alone.
Mine is slow to wake also, about a second. When its plugged into the charger its instant, weird.
I'm glad we aren't alone though. Hopefully if this is a big enough issue, people will look into it. And also, they've pulled the EB13 update from Sprint and Samsung's website.
It's causing problems with reading media from the SD card and also has data issues. So hopefully in the new one, they will fix this problem too?
Looks like it's No Lock, from what I can tell. If you disable it, it comes on instantly. If it's enabled, it takes it a moment to wake up.
My N4 was away to repair a broken screen. Got it back on Wednesday and it immediately updated to 4.3. All was well, except for one weird issue where hitting a notification from the pull down would take me to the app via the pattern lock. I put this down to having played with some lock screen settings in Setting Profiles app (trying to disable it in certain settings), but it might not have been.
I've done the first device restart today, and after rebooting there are a few big issues.
1. I don't appear to have any mobile network, though wifi is connected. I had a good signal before the reboot.
2. I'm not getting a lock pattern or any lock screen at all, and it's not asked for the SIM pin
3. Hitting a notification in the pull-down makes the 'lock' clicking sound as it takes me to the app
4. The home button doesn't work. I see a slight dim of the screen and it makes the lock click sound, but nothing happens. Back and multitask work fine
Help! Any ideas? Are they known issues? Can't seem to find any reference online.
I'm on stock, using Nova Launcher
!!11oneone said:
My N4 was away to repair a broken screen. Got it back on Wednesday and it immediately updated to 4.3. All was well, except for one weird issue where hitting a notification from the pull down would take me to the app via the pattern lock. I put this down to having played with some lock screen settings in Setting Profiles app (trying to disable it in certain settings), but it might not have been.
I've done the first device restart today, and after rebooting there are a few big issues.
1. I don't appear to have any mobile network, though wifi is connected. I had a good signal before the reboot.
2. I'm not getting a lock pattern or any lock screen at all, and it's not asked for the SIM pin
3. Hitting a notification in the pull-down makes the 'lock' clicking sound as it takes me to the app
4. The home button doesn't work. I see a slight dim of the screen and it makes the lock click sound, but nothing happens. Back and multitask work fine
Help! Any ideas? Are they known issues? Can't seem to find any reference online.
I'm on stock, using Nova Launcher
Click to expand...
Click to collapse
Those are not any known issues or anything I have read since Andrid 4.3 came out. Try a factory reset to see if that solves the problem. If not, maybe the screen wasn´t the only thing broken on your device. Ask for warranty.
Thanks, will see how I get on this evening and try a factory reset if it doesn't fix itself.
Seems to be a weird problem related to the lock screen and when it should/shouldn't kick in...
!!11oneone said:
Thanks, will see how I get on this evening and try a factory reset if it doesn't fix itself.
Seems to be a weird problem related to the lock screen and when it should/shouldn't kick in...
Click to expand...
Click to collapse
Glad I could help.
Ok, I've done a factory reset. Not had much chance to play as it took hours to reinstall everything. But I've just had the word issue where selecting something from the notification tray (the setting profiles shortcut) took me to the lock screen to put in my pattern first, then took me to the app.
EDIT no pattern to when it does it, seems random and can be while I'm using the device, so the lock screen shouldn't kick in for any reason
Any ideas? Faulty device?
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
Following the update to 5.1.1, when I switch on the Note 4 using the power button, the display fades in, slowly.
It takes ~1 second and is very annoying. I've been through display settings and a few other things, but nothing I do will make it appear instantly. I've tried a few web searches, but getting nothing relevant.
Anyone else see this? Anyone got a fix?
Thanks
Devany said:
Following the update to 5.1.1, when I switch on the Note 4 using the power button, the display fades in, slowly.
It takes ~1 second and is very annoying. I've been through display settings and a few other things, but nothing I do will make it appear instantly. I've tried a few web searches, but getting nothing relevant.
Anyone else see this? Anyone got a fix?
Thanks
Click to expand...
Click to collapse
Disable finger print lock.
Fingerprint lock was never enabled on the device. I figured that if someone wanted to steal it, I didn't want to motivate them to cut my finger off.
Also, I read the "Lag after 5.1.1 update", but assumed (!) that the fingerprint issue would not affect me because it had never been switched on.
On a hunch, I enabled fingerprint lock, then disabled it... problem resolved. Nasty.
Thanks.
Devany said:
Fingerprint lock was never enabled on the device. I figured that if someone wanted to steal it, I didn't want to motivate them to cut my finger off.
Also, I read the "Lag after 5.1.1 update", but assumed (!) that the fingerprint issue would not affect me because it had never been switched on.
On a hunch, I enabled fingerprint lock, then disabled it... problem resolved. Nasty.
Thanks.
Click to expand...
Click to collapse
Glad your issue resolved.
Hi, I've been using the essential phone for several days. I've installed lots of apps and other than a random glitch now and then, thinks have worked well. The system seems to be considerably faster than a Galaxy S8.
Two problems have recently surfaced. Smart lock is totally messed up (It was working for a while.) Now, when I get to the point in Security settings where I enter my pin, I get a blank screen. I've tried all sorts of things save a system reset. Smart Lock itself doesn't work any longer.
The other issue is intermittent freezes that last several seconds. Whatever the system is doing, it isn't responding at all. If I wait for a while, it proceeds to work fine.
Has anyone seen similar behaviors? Any suggestions short of a hard reset?
Thanks
charlie.s said:
Hi, I've been using the essential phone for several days. I've installed lots of apps and other than a random glitch now and then, thinks have worked well. The system seems to be considerably faster than a Galaxy S8.
Two problems have recently surfaced. Smart lock is totally messed up (It was working for a while.) Now, when I get to the point in Security settings where I enter my pin, I get a blank screen. I've tried all sorts of things save a system reset. Smart Lock itself doesn't work any longer.
The other issue is intermittent freezes that last several seconds. Whatever the system is doing, it isn't responding at all. If I wait for a while, it proceeds to work fine.
Has anyone seen similar behaviors? Any suggestions short of a hard reset?
Thanks
Click to expand...
Click to collapse
Did you perhaps add a company exchange account or add some other device administrator? I've seen this issue on some of my previous devices where smart Lock is setup but my company's exchange policy disables it
Sent from my PH-1 using Tapatalk
For smart lock goto settings -> security - >trust agents
Toggle smart lock off, return to settings, go back and toggle it back on. Smartlock is back to normal, atleast this did the trick for me.
Thanks to both of you for ideas. I disabled two device administrators, both related to Lookout. I also deleted my fingerprints and all security. When I re-entered everything, all seemed fine. I will see if it behaves and then narrow it down.
StephenMilone said:
For smart lock goto settings -> security - >trust agents
Toggle smart lock off, return to settings, go back and toggle it back on. Smartlock is back to normal, atleast this did the trick for me.
Click to expand...
Click to collapse
I had to do this but I had to reboot instead of just exiting out of settings.
I'm running into this issue as well. Sometimes I can get it to come back, but then after a restart, it's broken again...
---------- Post added 6th September 2017 at 12:14 AM ---------- Previous post was 5th September 2017 at 11:32 PM ----------
Ok, so it seems like the same issue is showing up for OnePlus devices since recently: https://forums.oneplus.net/search/13954406/?q=smart+lock&o=date&c[title_only]=1
I can get mine to freeze consistently by using chrome and browsing to flipboard.com. After I login the whole phone will freeze, not even the power button doesn't do anything. I've tested it out on a few other devices and I get the same response from my Nexus 9, also running 7.1.1. In this case at least I don't believe it's the phone but something to do with Android itself.
I'm getting the freeze as well but my power button works, when I turn off the screen and turn it back on it works for a few seconds and then freezes again
Sent from my PH-1 using Tapatalk
charlie.s said:
Hi, I've been using the essential phone for several days. I've installed lots of apps and other than a random glitch now and then, thinks have worked well. The system seems to be considerably faster than a Galaxy S8.
Two problems have recently surfaced. Smart lock is totally messed up (It was working for a while.) Now, when I get to the point in Security settings where I enter my pin, I get a blank screen. I've tried all sorts of things save a system reset. Smart Lock itself doesn't work any longer.
The other issue is intermittent freezes that last several seconds. Whatever the system is doing, it isn't responding at all. If I wait for a while, it proceeds to work fine.
Has anyone seen similar behaviors? Any suggestions short of a hard reset?
Thanks
Click to expand...
Click to collapse
You had the Smart Lock issue too?! I did a Factory Reset to fix it here, no amount of powering off/on the device, toggling Smart Lock in "Trust Agents" did the trick, it just...was blank one day. I've had the freezes as well, haven't noticed those after the Factory Reset now that I think about that.
RMarkwald said:
You had the Smart Lock issue too?! I did a Factory Reset to fix it here, no amount of powering off/on the device, toggling Smart Lock in "Trust Agents" did the trick, it just...was blank one day. I've had the freezes as well, haven't noticed those after the Factory Reset now that I think about that.
Click to expand...
Click to collapse
Interestingly, the pauses and stuttering disappeared at the same time. It is exceedingly difficult to convert these anecdotal comments into a meaningful diagnosis.
In any case, so far, so good.
Thanks! This is one of two major bugs driving me nuts!
Disabling then directly restarting worked for me, thanks for the tip!
Sent from my PH-1 using Tapatalk
I updated to NMl64c yesterday and both problems I refer to in the original post appear to have been fixed
charlie.s said:
I updated to NMl64c yesterday and both problems I refer to in the original post appear to have been fixed
Click to expand...
Click to collapse
The Smart Lock blank bug happened to me again yesterday, and I've been on NMI64c for a couple of days. De-activating Smart lock and rebooting got it working again.
Same problem with smart lock here and only solution seems to disable it, restart the phone and re-enable it...
Weird
Deppi0 said:
Same problem with smart lock here and only solution seems to disable it, restart the phone and re-enable it...
Weird
Click to expand...
Click to collapse
You should be able to disable it in the trust agents settings, back up one menu the enable it again without needing to restart the phone. Someone else pointed this it out a few posts back and it's always worked for me.
StephenMilone said:
For smart lock goto settings -> security - >trust agents
Toggle smart lock off, return to settings, go back and toggle it back on. Smartlock is back to normal, at least this did the trick for me.
Click to expand...
Click to collapse
1. Turn off all Smartlock agents that are on the list.
2. Reboot.
3. Turn them back on.
I have experienced a few freezes. Only after the phone sits for an extended period of time and it goes to sleep and after a restart. I actually haven't had this happen lately, seems like things some how worked themselves out. As far as smart lock I haven't had any such issue. I do have a question regarding smart lock. Do you guess have an option for enabling it when it is connected to a specific Bluetooth device?
jglazer said:
1. Turn off all Smartlock agents that are on the list.
2. Reboot.
3. Turn them back on.
Click to expand...
Click to collapse
Didn't have to reboot. Just turned it off then back on
Sent from my PH-1 using Tapatalk
jasonevil said:
Didn't have to reboot. Just turned it off then back on
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
All the on/off tinkering with trust agents has worked for me, but the fix has always been temporary. Smart Lock will be OK for a day or so before returning to its broken state/blank screen in the settings. Wish there was someone (a company) who knew what this was about and could fix it.