Pattern Lock wake-up is SLOW - AT&T Galaxy Note 3 Q&A, Help & Troubleshooting

I've posted a couple questions threads in the past few days so I hate to throw another one up here but this one is killing me.
Everything seems back to normal on my note except the fact that it takes 3-5 seconds for my phone to unlock after entering my unlock pattern. Another bug it has is that it wont set a pin unlock, you can enter the pin you want twice and it tries to save it but defaults back to a swipe unlock, It wont actually save the PIN unlock. It seems like it's having trouble cross checking the pattern or saving the pin to a file ... if that makes sense
I'm running this rom, odexed with an nc2 modem - Towel rooted and safe strapped.
I've been doing a lot of research and tried everything I've found, nothing has helped so far.
I've tried removing the sd, forcing GPU rendering, increasing animation times in dev. settings, clearing cache and dalvik, taking the personal message off of the lock screen, disabling watchON.
any ideas here at all?

You can Try the following (It worked for me on Galaxy S4 - Now it is smooth as butter flow)
1) Long press somewhere on the home screen so that you get change wallpaper option
2) Go to all options 1 by 1 and change wallpapers for all options.
3) Finally do a change wallpaper for Lock screen and Home screen.
This will resolve the problem of a sluggish unlocking pattern.
Hope it solves the problem!!

I have Galaxy A7.. Didn't expect it to solve with this funny tip.. And strangely it did.
Cheers mate.

That didn't work for me on galaxy a5 2016 running Android 7.0

Related

ICS stunner - lock screen flicker

When phone is locked, and I hit a button to unlock it, the HOME screen flickers for a second before the LOCK screen itself comes on...annoying but not a deal breaker. Any ideas on how to avoid this? I'm using the lock screen through euphoria, on quad skin. Thanks!
I was advised to disable 'CRT' in euphoria and clear cache...I disabled the 'CRT off animation' and cleared cache, rebooted, but it still happens when I go to unlock the phone!!
Any advice?
Same thing here it's just a minor bug with the ROM you could try searching the original thread and see if there is anything about it but I haven't had much luck finding anything. Version 4.4 of stunner is about to be released, maybe it will be addressed then.

[Fixed] Should I reset my phone?

I love the Moto X. Wanted one when it was first announced and I ended up buyiing the VZW DevEd through the Black Friday sale. Lately I have been having a lot of problems with my phone and Im not sure what is going on and if it is an app update or a system problems but I'll describe the issues I am having and will let you guys suggestion ideas of how to fix it.
1) When ever I open up the stock contacts app it is always saying "Contacts list is being updated". Some times I'll open it up and I can see all the contacts listed correctly but when I select a contact to view its details I just get a blank screen.
2) This might be due to the contacts app, but when every I receive a phone call from a known contact the phone app only provides me with the phone number and not exactly who the caller is as defined in the contacts. Also when I receive a phone call while the phone is locked with the screen off the screen does not light up but the ring tone is played. Even picking up the phone does not light up the screen. I have to hit the lock button which silences the phone then hit it again to light the screen up then I can select answer or end call. Thats all hoping the caller is still callling me as this process takes a while.
3) Kind of the samething above but with the stock clock app and an active alarm. The phone has been super laggy that I can't silence or snooze and alarm in the morning quickly. I have to place my finger on the ring wait a few seconds to see it light up that I have selected the ring then I can move it to dismiss or snooze. When I select one of those options and let go it will pause on the screen and stay light for 10 seconds and then the selection will process correctly
4) This may be subjective but I think my battery life right now is really bad. I check the battery stats and it seems fine but when I use it the battery seems to drain really fast.
5) This isn't subjective. Everything is laggy from loading an app to displaying the recently used apps. I've tried uninstalling things, disabling things, enabling things and nothing seems to work. Its especially laggy when going from phone locked screen off to the home screen. It is no where as responsive as it once was. I was even down to 4GB of storage left out of 32GB so I cleared a bunch off the SD card and still its laggy.
So what do you guys think? Should I reset the phone or has someone experienced something similar and knows how to fix it. FYI, I am using Apex Pro as my launcher.
Talguy said:
I love the Moto X. Wanted one when it was first announced and I ended up buyiing the VZW DevEd through the Black Friday sale. Lately I have been having a lot of problems with my phone and Im not sure what is going on and if it is an app update or a system problems but I'll describe the issues I am having and will let you guys suggestion ideas of how to fix it.
1) When ever I open up the stock contacts app it is always saying "Contacts list is being updated". Some times I'll open it up and I can see all the contacts listed correctly but when I select a contact to view its details I just get a blank screen.
2) This might be due to the contacts app, but when every I receive a phone call from a known contact the phone app only provides me with the phone number and not exactly who the caller is as defined in the contacts. Also when I receive a phone call while the phone is locked with the screen off the screen does not light up but the ring tone is played. Even picking up the phone does not light up the screen. I have to hit the lock button which silences the phone then hit it again to light the screen up then I can select answer or end call. Thats all hoping the caller is still callling me as this process takes a while.
3) Kind of the samething above but with the stock clock app and an active alarm. The phone has been super laggy that I can't silence or snooze and alarm in the morning quickly. I have to place my finger on the ring wait a few seconds to see it light up that I have selected the ring then I can move it to dismiss or snooze. When I select one of those options and let go it will pause on the screen and stay light for 10 seconds and then the selection will process correctly
4) This may be subjective but I think my battery life right now is really bad. I check the battery stats and it seems fine but when I use it the battery seems to drain really fast.
5) This isn't subjective. Everything is laggy from loading an app to displaying the recently used apps. I've tried uninstalling things, disabling things, enabling things and nothing seems to work. Its especially laggy when going from phone locked screen off to the home screen. It is no where as responsive as it once was. I was even down to 4GB of storage left out of 32GB so I cleared a bunch off the SD card and still its laggy.
So what do you guys think? Should I reset the phone or has someone experienced something similar and knows how to fix it. FYI, I am using Apex Pro as my launcher.
Click to expand...
Click to collapse
Try resetting your phone, if that doesn't work, then talk to motorola support. This stuff shouldn't happen and I'm sure Motorola's support team will be happy to help you.
danny39 said:
Try resetting your phone, if that doesn't work, then talk to motorola support. This stuff shouldn't happen and I'm sure Motorola's support team will be happy to help you.
Click to expand...
Click to collapse
So I think I fixed the problem last night with out resetting the phone based on something I mentioned here. I stated that I'm using Apex as my launcher. Not sure why I didn't think of this before, but last night I decided to change back to the stock launcher and closed out of apex in the recent apps menu. Everything got super snappy when going from view to view and launching apps. I then loaded Apex back up and it all seemed to work just fine. This morning when my alarms went off I didn't experience the problem that I was describing about above.
So I'm going to consider this issue fixed, however I will keep an eye on it to see if it comes back.

To update to MM or to not

Well the update finally hit and now I'm looking for anybody who is using it to share their experience(s). I'm scarred by the G3 update to Lollipop which basically broke the phone but that's another story. Does anybody know of a known bug list or anything like that which is being compiled?
Cheers
I like it. Haven't ran into any problems yet. I didn't OTA. I downloaded the firmware, factory reset my phone, then flashed via Odin.
Im running it for 2 days now, rooted and viper4android working. I love it. Battery life is good, Deep sleeps like it should. Very snappy and they made some minor changes to the UI. Just waiting on a fully compatible kernel now
---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------
troby86 said:
I like it. Haven't ran into any problems yet. I didn't OTA. I downloaded the firmware, factory reset my phone, then flashed via Odin.
Click to expand...
Click to collapse
I did the same, some say dont but i like change and this one is a good change
I just flashed the stock T-Mobile 6.0 firmware this morning. One change that annoys me is the swipe to unlock screen. I use pattern to unlock my phone. On 6.0 I get this screen before I can input my pattern, so it is an unnecessary extra step to unlock my phone. Very annoying.
I updated about two days ago, so far I like it a lot. My device seems to be running a lot smoother than before. Feels much better to me.
Sent from my SM-G925T using XDA-Developers mobile app
HKSpeed said:
I just flashed the stock T-Mobile 6.0 firmware this morning. One change that annoys me is the swipe to unlock screen. I use pattern to unlock my phone. On 6.0 I get this screen before I can input my pattern, so it is an unnecessary extra step to unlock my phone. Very annoying.
Click to expand...
Click to collapse
Wait till you use fingerprints to unlock the device, they have updated some security policy so they need secondary unlock method along with fingerprint to unlock the phone, that's very very annoying.. thinking of replacing fingerprint lock all together
soumik shah said:
Wait till you use fingerprints to unlock the device, they have updated some security policy so they need secondary unlock method along with fingerprint to unlock the phone, that's very very annoying.. thinking of replacing fingerprint lock all together
Click to expand...
Click to collapse
Ummm...no. The secondary unlock is a backup for the fingerprints. You don't have to do both to unlock the phone. Just verified, turned the screen on, and held my finger in place...boom, unlocked.
Just when you restart the phone you need to put the secondary unlock method.
Phone is very fluid and I love it, best update i had in a phone in a long time.
Just 1 thing and I bet you'll like it.
No more laggy.
Sent from my SM-G920T using XDA-Developers mobile app
Wow first time I've seen a SW push on a phone that everybody seems to be pretty satisfied with lol. I took the plunge this morning and noticed the secondary password for fingerprints as well. However I know that's always been there as a back up and for whatever reason it had to be reset on the first boot but it's gone away now and is only a back up when it doesn't recognize my fingerprint more than three times. So far so good, I'm curious to see if there is any improvement on the battery life or not.
Thanks for the info everybody!
After I updated my phone to 6.0.1, I did a factory reset. I couldn't be happier. I use fingerprint unlock and have my phone encrypted. Since the release (4/11), I haven't had any issues with battery or performance. I did notice that the auto-brightness seems to be more aggressive than Lollipop. One issue I didn't like was that when I used All-In-One-Gesture to enable double-tap to sleep, I had to manually type my password every time to unlock the phone. I think because of my security settings (allowing an app to have permission to lock the screen), I wasn't able to fingerprint unlock unless I manually turned off the screen using the power button. Otherwise, I don't mind entering a long password every time I turn on the phone.
In standby, my phone would drain 15%-20% over 8 hours each night while I slept. With MM, my phone drains less than 5% each night now.
Anyone having problems with LED notifcations not working? It works when I'm charging, but not any other time. It is turned on in settings>display. I also made sure notifications settings for my apps were not blocked. Weird. So far I'm unimpressed by MM. Alot of things don't work right, like LED notifications The battery improvement is negligible. I was getting 5% battery loss overnight anyway. I didn't do a factory reset before/after upgrading. Maybe that will fix my problems.
Update: I fixed the LED notification by doing a factory reset in recovery. Now I have to reinstall everything . My phone is stock by the way.
it works pretty good all around ui is smooth it has a refined feel compared to the older updates
Sent from my SM-G920T using XDA-Developers mobile app
Battery life has been MUCH better for me.
Rooted+ Xposed. I even disabled the location wakelock module I HAD to use in LP, and it's still much better. SOT isn't really effected much, but screen off + listening to streaming music has more than halves battery usage for me, along with idle time.
Tthe phone is much smoother, and I have not experienced any lagging (have animations turned off, though). Plus, finger print unlock is tons faster. LP always lagged hard for me there, now it's almost as fast as the wife's 6s+.
I got a small issue with unlock function.
If I made screen of my hard button, I could use fingerprint to unlock the screen, but if I used 3rd-app to make screen off, I need to use back up method - PIN to unlock the screen.
Does anyone face the same issue?
Received the OTA update. I'm on stock.
Battery life is *slightly* better, but it's nothing to write home about.
The auto-brightness has been updated, and I feel it's not for the better. It seems to dim/brighten aggressively, and/or not work at all. It's been irritating.
trungctu said:
I got a small issue with unlock function.
If I made screen of my hard button, I could use fingerprint to unlock the screen, but if I used 3rd-app to make screen off, I need to use back up method - PIN to unlock the screen.
Does anyone face the same issue?
Click to expand...
Click to collapse
I have that problem too. I forget which security setting it is, but basically it requires you to enter your password whenever an app locks the screen. I don't think there is any way around it. I uninstalled all my apps that lock the screen, except greenify, for that reason.
drbongles44 said:
I have that problem too. I forget which security setting it is, but basically it requires you to enter your password whenever an app locks the screen. I don't think there is any way around it. I uninstalled all my apps that lock the screen, except greenify, for that reason.
Click to expand...
Click to collapse
Me too... back to stock "easy touch" and wait for next update...
Sent from my SM-G920T using Tapatalk
Great update
If you stick with the stock marshmallow update I think you will be happy. You are able to root it also without a problem.
If you make sure NFC and WiFi are turned off (When you're not using them) I personally have seen better battery usage than Lollipop.
I'm running the stock rooted marshmallow and it really is a beautiful update with a bunch of enhanced features. I would recommend.
As a bonus, it also gives your phone a radio update (which allows it to better contact T-mobile's towers).
If you really want a boost in speed, you should lookup changing your APN settings to force your phone into IPv4, because currently your phone will default to IPv6 which (at least for me) is a tad slower than IPv4.
Good luck and have fun messing around with the new update
HKSpeed said:
I just flashed the stock T-Mobile 6.0 firmware this morning. One change that annoys me is the swipe to unlock screen. I use pattern to unlock my phone. On 6.0 I get this screen before I can input my pattern, so it is an unnecessary extra step to unlock my phone. Very annoying.
Click to expand...
Click to collapse
yeah I'm with you on that.
Another thing that is annoying me, and maybe there is a setting to turn this off (if so please tell me as I've not yet found or really looked into it yet)...
It used to be that when I opened a link it would prompt me which browser or or program I wanted it to open with. I actually like being prompted each time because sometimes I want this a bit more secure and so would open with Orweb vs. Google.
Now it seems that once I select and option it becomes the default option until I go in and change it.
Otherwise, I'm enjoying it. I'm rooted running xposed and viper etc.
I really do want my gradient status bar back though...

LE S3 random reboot itself & fingerprint lost function.

LE S3, unrooted, using nova launcher. Two sim cards: one is ATT, the other is China Unicon(roaming on ATT). Just had the phone about three weeks.
My S3 often reboot itself, during text message, or browsing, or playing youtube, or in some apps, or even it is screen off resting on my desk. I couldn't find a pattern.
I performed factory reset and install about 10 frequently used apps. It has just 1 reboot over last 24 hours. I was cast youtube to chromecast and the phone was screen off and resting.
Another annoying issue is the fingerprint randomly lost function, it refuses my fingerprint. If I tried to add a new fingerprint, it prompted let me clean my finger and fingerprint identifier. Usually a reboot will solve the issue. But sometime it lost fingerprint function after a reboot.
Does anyone have similar experience? what could be the cause of those two issues? Is there any debugging log that can be checked? Should I contact support to get a fix/replacement?
Any help is appreciated!
Thanks.
Replace You're Phone..

Frozen screen after waking up screen

At some point after upgrading to Android 9 I started having the following issue where if the screen turns off due to inactivity and I turn it back on by pressing the power button, I see whatever screen I had open before it went to sleep but it's frozen. Scrolling touching etc still perform (invisible) actions but the screen is frozen until I either press the app switch button or perform some action that would change the current application. While the screen is frozen the drawer from the top works just fine. Also when the app that gets frozen is the desktop (I'm using the default launcher), I can see the background scrolling if I swipe left or right but the widgets don't change, they are frozen.
Does anyone else have the same problem? Any ideas what could be causing it?
Tritonio_GR said:
At some point after upgrading to Android 9 I started having the following issue where if the screen turns off due to inactivity and I turn it back on by pressing the power button, I see whatever screen I had open before it went to sleep but it's frozen. Scrolling touching etc still perform (invisible) actions but the screen is frozen until I either press the app switch button or perform some action that would change the current application. While the screen is frozen the drawer from the top works just fine. Also when the app that gets frozen is the desktop (I'm using the default launcher), I can see the background scrolling if I swipe left or right but the widgets don't change, they are frozen.
Does anyone else have the same problem? Any ideas what could be causing it?
Click to expand...
Click to collapse
FWIW I have not really solved the problem but I am circumventing it by having the screen lock immediately instead of waiting 5 minutes. That way I have to unlock with a fingerprint every time the screen is off, and unlocking refreshes the screen which "fixes" the problem.
Tritonio_GR said:
FWIW I have not really solved the problem but I am circumventing it by having the screen lock immediately instead of waiting 5 minutes. That way I have to unlock with a fingerprint every time the screen is off, and unlocking refreshes the screen which "fixes" the problem.
Click to expand...
Click to collapse
There were lot of reports of glitchy phones after the Pie update.
The cure was a factory reset or software repair with Xperia Companion
Use Xperia Transfer to back up your calls/contacts/texts before you reset the phone
Didgesteve said:
There were lot of reports of glitchy phones after the Pie update.
The cure was a factory reset
Click to expand...
Click to collapse
Can you please link a thread, where users told, that problem is solved after reset?
I have the same frozen display (since Android Pie), when turning display off and on again.
Don´t wish to reset and install all again, if that does not help.
bye,
Ralf
thegrobi said:
Can you please link a thread, where users told, that problem is solved after reset?
I have the same frozen display (since Android Pie), when turning display off and on again.
Don´t wish to reset and install all again, if that does not help.
bye,
Ralf
Click to expand...
Click to collapse
Hi Ralf,
the phone will always work better with a reset after a major update, all the Oreo applications are trying to work under Pie. Sometimes it works, sometimes it doesn't. Oreo apps aren't made to work under Pie and they can error.
here, is one example, or another, but I didn't jump to Pie because of all the negative feedback and the scores of people trying to downgrade.
A reset will fix your problem and if you use Xperia transfer then the amount of personal information lost will be minimal.
Thanks for the links.
Didgesteve said:
all the Oreo applications are trying to work under Pie. Sometimes it works, sometimes it doesn't. Oreo apps aren't made to work under Pie and they can error.
Click to expand...
Click to collapse
This sounds to me, the combination of "old" Navi-apps with Pie is the problem. May be only with Pie on some Sonys.
I'm afraid, a reset will not change the frozen display.
All other apps till now do not freeze after display-on except MagicEarth and Osmand+
This 2 apps i deinstalled (+ deleting the data) and installed again.
A reset will fix your problem and if you use Xperia transfer then the amount of personal information lost will be minimal.
Click to expand...
Click to collapse
Xperia transfer shows me only 2 apps for backup.
I'll probably try a reset in the next few days anyway.
bye,
Ralf
thegrobi said:
Thanks for the links.
This sounds to me, the combination of "old" Navi-apps with Pie is the problem. May be only with Pie on some Sonys.
I'm afraid, a reset will not change the frozen display.
All other apps till now do not freeze after display-on except MagicEarth and Osmand+
This 2 apps i deinstalled (+ deleting the data) and installed again.
Xperia transfer shows me only 2 apps for backup.
I'll probably try a reset in the next few days anyway.
bye,
Ralf
Click to expand...
Click to collapse
Looks like there is know issue with the Osmand+, the date of the post is may last year, but it may just be a 'feature'
When backing up with Xperia transfer, make sure you select all the boxes that are optional. It's things like text messages/contacts/phone history that are useful after a reset. Some apps can't be moved and have to be downloaded directly from the playstore, but Google should give you that option, after you log back in to the wiped phone.
Edit: I can recomend Sygic, free maps for one country, works without data.
In the meantime, I found more users with this problem and a little solution that another user describes:
I can confirm I have the exact same issue since Android 9 with my Xperia xz1 compact.
I normally have no lockscreen options set. So when I wakeup the Phone, it sometimes kind of 'locks' the screen. Widgets do not respond, I cannot switch home screens. The time on the status bar remains correct. If I then click on an app and go back, everythning behaves normally.
So I'm quite sure this must be a software issue, as other people have this problem to.
My workaround for now is to have a lockscreen option aktive. But I would rather have not, for conveniance.
I tested this also with safe mode and complete factory reset of the phone. The 'bug' is still there.
Click to expand...
Click to collapse
If I disable lockscreen, then apps stop when it is switched on again. However, I always have to enter pin or use fingerprint sensor, or smart lock.
This often does not work when cycling and is dangerous when cardriving.
On Android 8, the lockscreen did not need to be active.
So the problem is not Osmand and MagicEarth.
It is a Sony 9 bug with Android 9.
bye,
Ralf
Found in an other forum an easy method to reproduce the problem.
disable the screen lock (it must be set to "None");
lock the phone and then unlock it;
lock and unlock it again.
Click to expand...
Click to collapse
bye,
Ralf
---------- Post added at 01:50 PM ---------- Previous post was at 01:20 PM ----------
Because I believe that Sony will not fix the error, I could imagine a solution:
An app (possibly tasker), which puts a selectable running app from foreground while pressing the power button in the background and immediately brings it back to the foreground.
Does anyone know such a tool?
bye,
Ralf
[/COLOR]Because I believe that Sony will not fix the error, I could imagine a solution:
An app (possibly tasker), which puts a selectable running app from foreground while pressing the power button in the background and immediately brings it back to the foreground.
Does anyone know such a tool?
bye,
Ralf[/QUOTE]
So, did you ever find a solution?

Categories

Resources