[~fix] Huge lag after 4.4.2 update - Galaxy Note 3 Q&A, Help & Troubleshooting

Hi everyone ...
[Updated in post #3]
I faced a terrible lag with my SM-900 after 4.4.2 update and I read a lot about this bad combination (S View + Lock with PIN) but I was forced to use the lock screen bcz of the company email server.
So, I decided to go into some experiments:
- Wiped cache partition: didn't solve
- Flashed stock Rom: didn't solve
- Used stock cover: didn't solve
- Removed the exchange account and lock screen: didn't solve
So, I decide to start from scratch. I flashed the stock rom with Odin then a factory reset without the S View cover. I didn't install except very few apps (FB, Whatsapp and viber). The lag disappeared and the system was snappy and very smooth. After couple of days I put the S View cover and the system kept running smooth as is. After another couple of days I enabled the lock screen with PIN and the system is still in a very good shape and the clock of the lock screen always shows the right time and the home button response to wake up is perfect.
That eliminates the theory of SV+LS cause of lag. However, I 'll wait for few days then I will configure the company exchange account and update this post again.
Hope this is useful for some people who's facing this annoying problem.

Biso007 said:
Hi everyone ...
I faced a terrible lag with my SM-900 after 4.4.2 update and I read a lot about this bad combination (S View + Lock with PIN) but I was forced to use the lock screen bcz of the company email server.
So, I decided to go into some experiments:
- Wiped cache partition: didn't solve
- Flashed stock Rom: didn't solve
- Used stock cover: didn't solve
- Removed the exchange account and lock screen: didn't solve
So, I decide to start from scratch. I flashed the stock rom with Odin then a factory reset without the S View cover. I didn't install except very few apps (FB, Whatsapp and viber). The lag disappeared and the system was snappy and very smooth. After couple of days I put the S View cover and the system kept running smooth as is. After another couple of days I enabled the lock screen with PIN and the system is still in a very good shape and the clock of the lock screen always shows the right time and the home button response to wake up is perfect.
That eliminates the theory of SV+LS cause of lag. However, I 'll wait for few days then I will configure the company exchange account and update this post again.
Hope this is useful for some people who's facing this annoying problem.
Click to expand...
Click to collapse
Hi,
Please keep updating about this LAG issue. I have the same problems and have the same configuration of corporate exchange email and PIN lock.
Did not find a solution for the lag yet.
Thanks!

Update:
I configured the Exchange account for 5 days now. The device is still working very fine with no "noticeable" lag. However, I have noticed the following:
- for only once the screen didn't come on with an incoming phone call.
- Now the clock on the lock screen always doesn't match the system clock when you flip the S View cover.
Conclusion: I tend to believe that 4.4.2 for Note 3 has a bug somewhere in the lock screen process, and this bug is building the lag issue with time. Also, I believe as well that the OTA process for 4.4.2 on top of existing data brings this issue very fast. I think the best way is to do a factory reset then update/flash the device with the stock 4.4.2 (through Odin) then to start by enabling the lock screen with PIN before configuring the Exchange account.
I don't have a scientific explanation to prove this will work for everyone, but that what worked for me

Related

Stock Froyo Pin lock causes boot problems

Using Froyo, when setting a PIN lock (now required for exchange) boots take a *very* long time... sometimes 10 minutes or more. Watching the status bar at boot it seems to "restart" at a certain point in the boot process many times. I've captured a log with ADP and I see a number of fatal errors, but nothing I can relate directly to the pin lock.
I confirmed the same problem on my wife's Vibrant (pretty much straight stock w/o a lot of apps).
Pattern lock works fine. (but not allowed by exchange). Password lock behaves the same way.
I posted on the T-Mobile forums and others there confirmed the problem but no solution. I don't think T-Mobile will be fixing this anytime soon... do other ROMs have the same issue? Is there a simple fix?
Robert
I had the same problem using the pin lock. When I rebooted it got stuck in the "media scanner" loop with random vibrating from the phone. I had to format my sd card to get back on, on the third time it did this it forced me to factory reset just so I could use the damn phone again. I got so fed up I decided to look into rooting my phone. I was able to root it and haven't looked back since. If samsung ever decides to send out more updates I'll never do it until team whiskey takes a look at it and makes it better . I went back to 2.1.1 eclair stock, cuz I wasn't able to do it with 2.2 froyo (cuz I'm new). I'm now using bionix v1.2.1, its pretty awesome. I had used the pin lock with this rom and it works just fine, haven't tried the pattern lock or other password lock. I don't use it anymore but it has nothing to do with it being unstable, just personal. Anyway, if you're looking into rooting I highly recommend bionix-v. Good luck with your phone
I am rooted, but you're talking about running a non-stock ROM. I don't feel the need for it (yet).
stock Exchange email forced the use of a pattern or password lock. I've started using touchdown and it just requires the pin lock in the touchdown app, not the whole phone. I'll probably stick with the stock ROM and Touchdown.
I find it strange that something like a screen lock would cause so much trouble.
Robert

[Q] Soft reboot on Lock-unlock-Lock-unlock

I am using the D802, bought it in Singapore under M1. I also use the flipcover with the quick window - bug does not happen when i unlock using it. On stock with TWRP and root.
The problem first started when I rooted my device, I noticed that locking it and quickly unlocking it again would sometimes cause a soft reboot. The problem went away after a while, but today it has rebooted on me at least 8 times.
My logcat is attached below(no confidential stuff there). I seem to be able to reproduce the problem pretty easily today, so I started logging from when I turned on my screen and ends when the phone shows the lock screen when I finish the boot(when the lock screen appears)
Unlocking is attempted the moment the screen turns on and all the widgets have loaded(1second?), and the soft reboot occur both with double tap and using the power on key.
https://docs.google.com/file/d/0B3ooqFjmbeiFZDg3aHVUenFCWWc/edit?usp=sharing
I've already done a cache and dalvik cache wipe using TWRP 2.6.3.2 but it does nothing IMO
Any one has any ideas? I suspect a problem with me /system/bin/cnd file cos is keeps showing a "reading a NULL string not supported here" - it's the one error that keeps showing up. Any help would be really appreciated, thank you so much
I have seen this problem on many, many occasions with my T-Mobile G2 but in my case I did not dug that deep (logcat).
However I noticed the problem occurred while using either the Lockscreen Gmail Widget or the Launcher Gmail Widget.
Once I remove them, the problem is gone.
Cheers!
I see, thank you so much! Just removed it.
Rayan said:
I have seen this problem on many, many occasions with my T-Mobile G2 but in my case I did not dug that deep (logcat).
However I noticed the problem occurred while using either the Lockscreen Gmail Widget or the Launcher Gmail Widget.
Once I remove them, the problem is gone.
Cheers!
Click to expand...
Click to collapse
WOO. I thought I ****ed up my phone when flashing TWRP but you found it out Cheers. Going to submit bug report to gmail so they can take a look at this.
I don't wanna sound tacky, but saying thanks through the Thanks button is best!!!
Glad it helped!

[Q] Random unresponsive home and lock button

Hi,
I am having some serious trouble with my note 3.
The basics of the problem are that the lock button seems to lock the screen but once pressed again it shows whatever was on the screen before, not the lock screen!? Holding the lock button does not come up with the turn off/reset options.
Another odd thing that happens along with this is that any application that is opened or closed the screen flashes black before opening up.
Along with this I have found that the alot of the native apps, including phone, contacts and most annoyingly, CLOCK, crash also. Making me late for work and rendering the phone useless unless I do a battery pull.
I will note that the most odd thing is that I contacted our business contract guy who who i expected to tell me to do a soft reset, told me that the supplier would swap out the phone?! That was last week and the new handset is showing early signs of the same thing.
Neither phones are rooted and I have not installed any unknown sources on the new handset to be sure it wasnt an outside source?!
Any help would be appreciated.
HAJ32 said:
Hi,
I am having some serious trouble with my note 3.
The basics of the problem are that the lock button seems to lock the screen but once pressed again it shows whatever was on the screen before, not the lock screen!? Holding the lock button does not come up with the turn off/reset options.
Another odd thing that happens along with this is that any application that is opened or closed the screen flashes black before opening up.
Along with this I have found that the alot of the native apps, including phone, contacts and most annoyingly, CLOCK, crash also. Making me late for work and rendering the phone useless unless I do a battery pull.
I will note that the most odd thing is that I contacted our business contract guy who who i expected to tell me to do a soft reset, told me that the supplier would swap out the phone?! That was last week and the new handset is showing early signs of the same thing.
Neither phones are rooted and I have not installed any unknown sources on the new handset to be sure it wasnt an outside source?!
Any help would be appreciated.
Click to expand...
Click to collapse
Factory Reset
if not solve ur problems, try Odin flash tools to flash another stock ROM
if not work take to service cause it should be hardware problem.
:good:
x102x96x said:
Factory Reset
if not solve ur problems, try Odin flash tools to flash another stock ROM
if not work take to service cause it should be hardware problem.
:good:
Click to expand...
Click to collapse
But why would the problem occur on two separate brand new devices?
because you have the same app on both phones :highfive:
dancapitan said:
because you have the same app on both phones :highfive:
Click to expand...
Click to collapse
lol....any suggestions what sort of app?
Does it also happen before you install any apps?
Send From My Samsung Galaxy Note 3 N9005 Using Tapatalk
ShadowLea said:
Does it also happen before you install any apps?
Send From My Samsung Galaxy Note 3 N9005 Using Tapatalk
Click to expand...
Click to collapse
Well some of my apps install straight onto the phone.
Do you think I should remove as many as possible and try then?
Same exact issue here
HAJ32 said:
Hi,
I am having some serious trouble with my note 3.
The basics of the problem are that the lock button seems to lock the screen but once pressed again it shows whatever was on the screen before, not the lock screen!? Holding the lock button does not come up with the turn off/reset options.
Another odd thing that happens along with this is that any application that is opened or closed the screen flashes black before opening up.
Along with this I have found that the alot of the native apps, including phone, contacts and most annoyingly, CLOCK, crash also. Making me late for work and rendering the phone useless unless I do a battery pull.
I will note that the most odd thing is that I contacted our business contract guy who who i expected to tell me to do a soft reset, told me that the supplier would swap out the phone?! That was last week and the new handset is showing early signs of the same thing.
Neither phones are rooted and I have not installed any unknown sources on the new handset to be sure it wasnt an outside source?!
Any help would be appreciated.
Click to expand...
Click to collapse
I am having this same exact issue. First happened when I installed a SanDisk Ultra CLASS 10. I thought the card was causing me compatibility issues so I returned it to amazon. This was just a few days ago. The only thing that worked to fix this issue was to remove the battery.
On the way to work today I suddenly couldn't play any music downloaded from Google music to my device. However, I could stream music that was not downloaded to my device. I also couldn't view any pictures in my picture gallery. I tried rebooting the phone and guess what -- I got the same exact issue as the original post above.
I wasn't going to mess with my phone while driving so I made up my mind that I was going to return it to verizon tomorrow. About an hour into work I picked up my phone and it gave me the onscreen instructions to swipe up to get flip board -- same instructions it gives you after a reboot. I then tried playing the same music that wouldn't play before and it played. I tried viewing pictures in the gallery that were inviewable before and they were now viewable.
I'd like to know what is going on too. I can't just give up to the fact that my phone doesn't want to work at certain times of the day so I just have to give it an hour.
HAJ32 said:
Well some of my apps install straight onto the phone.
Do you think I should remove as many as possible and try then?
Click to expand...
Click to collapse
The best thing would be to remove all non-factory apps. But yes, start by removing as many of them as possible.
(If that doesn't work, do a factory reset and cache wipe through the recovery menu, and don't restore a single app. (I'm not talking abouy the bloatware, we all have those.))
If there are no problems at that point, add back your apps one by one. (no restoring anything, make sure they are clean installs.)
Eventually you should run into whatever app is causing the issue.
Send From My Samsung Galaxy Note 3 N9005 Using Tapatalk
Same issues
ShadowLea said:
The best thing would be to remove all non-factory apps. But yes, start by removing as many of them as possible.
(If that doesn't work, do a factory reset and cache wipe through the recovery menu, and don't restore a single app. (I'm not talking abouy the bloatware, we all have those.))
If there are no problems at that point, add back your apps one by one. (no restoring anything, make sure they are clean installs.)
Eventually you should run into whatever app is causing the issue.
Send From My Samsung Galaxy Note 3 N9005 Using Tapatalk
Click to expand...
Click to collapse
I reset the system to factory settings and started arranging only the installed apps and widgets and I got the same lock screen issues.
This time the phone wouldn't go to the lock screen but it would give me the option to restart or shut down. I set it aside again and when I picked it up a few later it showed me the home screen wwith instructions on how to access flipboard -- as if it was reset! I have a warranty on mine so I'm gonna return it to verizon tomorrow or friday.

Fingerprint hardware not available and screen locks itself immediately!

Hi everyone!
I have a OP 2 for more than one and a half years now and never had any issues with it(stayed stock...) until recently. I didnt update the phone to the latest version and was putting it off, and today in the afternoon when I tried to unlock my phone it said the 'Fingerprint hardware is not available' and after unlocking the phone with the pattern, it IMMEDIATELY LOCKS ITSELF BACK !!! after split second it just locks the screen while everything is working like connection, wifi, messages, notifications, etc. but due to this I cannot access anything on the phone, can't go to settings and switch to onscreen nav bar buttons, can't force stop/wipe cache the com.fingerprints.serviceext either, tried restarting it several times, downloaded the update but can't even install it because the phone just locks!:crying: I have no idea what would fix it and I am avoiding a full reset and wipe on the phone(also based on all i have read, dont think it would fix it anyways)
If anyone knows whats the problem or has dealt with it or knows someone who has, please help me out here on how to fix this and what to do. I did not root it or flash custom ROM's on it yet and never had a flip cover or any sort of case so literally don't know why it happened.
Thanks in advance,
Max
Hi
I had the exact same issue with mine, I was on LineageOS and could access the logs so I was able to determine it was an hardware failure.
Went to a repair shop to replace the home button, and Bam it worked again.
If you didn't flash a custom ROM it is likely an hardware issue just like I had.

Somebody else having problems with their fingerprint reader?

Hi, first of all I apologise if this question has been asked but I don't know how to search just this place.
I'm using everything stock, no root, stock launcher.
I have my phone set up to ask for the password on reboot. I have my fingerprint reader set up to unlock my phone. I also have the fingerprint reader set up to wake the screen.
However under certain circumstances the fingerprint reader does not unlock the phone. The most reliable way to trigger this behavior is to plug the phone in to charge.
I exclusively lock the screen with the power button.
The fingerprint reader is still responsive and it still wakes the screen but there's no vibration feedback and it does not unlock. After I unlocked the phone with my password and lock it again the reader works again.
So what's going on here? How should I debug this?
After reboot it is normal to ask for password first time. Sometimes i have also seen this but when i unlock with pattern (my backup way) and lock again it works fine. I can not trace this to be related with charging or something else and it happens rarely but i have seen it also. Maybe a software bug.
Looking back to the days when i have LG V10 i remember that i had the same problem with fingerprint sensor not working sometimes. It was more frequently related to heat buildup as it was hot phone anyway.
I had the same problem these days, I think the fingerprint reader won't work if your hands are really cold.
Hmm I don't think my U Ultra is getting particularly hot and, no, my hands are certainly not very cold either. This behavior happens indoors.
It's just extra security plan and simple
Sometimes, not very often though, my fingerprint reader refuses to respond. Not even a misread where you get haptic feedback and not a lot else.
Just using the power button and entering my back up security (pattern in my case) and it comes back to life.
I don't particularly worry about it, but I suppose it's nice to see that it's not just me
Will see if the upgrade to 8.0 fixes it.
I met this problem.The solution was very interesting.I use Yandex.disk app.This problem did occur after the Yandex.disk app is update.I hard reset my phone.The problem was not in my phone.But I setup Yandex.Disk app the problem repeat occur.İf you installed Yandex.Disk, uninstall the application.if you don't use Yandex.Disk,The last apps update uninstall to try.
Good Lord I have so many apps installed though...
Then go to a full factory reset and see if it helps, thats the 1st thing you do when you have problem.
After a bit of experimentation this behavior seems to have stopped after I disabled/removed all Smart Lock Trusted Places -- a feature that is already known to be buggy.
I have it too, once a day it puts me to enter the password, its a security or a bug idk.
No more, no less, every time when its charging. I installed some 3rd party apps, its possible that they are to blame.
We will see when 8.o strikes and i will hard reset.
Garkan said:
I have it too, once a day it puts me to enter the password, its a security or a bug idk.
No more, no less, every time when its charging. I installed some 3rd party apps, its possible that they are to blame.
We will see when 8.o strikes and i will hard reset.
Click to expand...
Click to collapse
8 fixed this bug for me but i found more bugs in oreo so i am thinking to roll back to 7.0 and meet fingerprint sensor bug again because oreo problems are disgusting - car bluetooth does not works as it should - i can't read addressbook in my car head unit - it shows error. i found that is some bluetooth software parts was not included in 8.0 but successfully fixed in 8.1. and i'am pretty sure we will never receive 8.1 for u ultra.
in russian 4pda forum i found some reports (unconfirmed yet) that fingerprint bug disappeared. maybe somebody here can confirmed it?
No i have android 8 and issue still occurs sadly did not found a fix.
I've suddenly had this issue a couple of days ago a couple of times. I didn't do anything (except a couple of reboots) and it was fixed again.
Now after updating to Oreo and again using leedroids ROM, i didn't experience theissue again..
I talked to a htc representative and said to clear credentials from security/encryption and credentials seems to be a conflict in security certificates. For the moment it works.

Categories

Resources