Unlocking lag/delay on RR-OS - Xiaomi Redmi Note 5 Pro Questions & Answers

Hi fellas, I'm currently on my favourite ROM (Resurrection remix) from all time. I use fingerprint unlock and when I place my finger, the phone unlocks but screen takes longer to turn on (up to a minute in the worst case)
Yes, you heard me, turn on, the phone is unlocked, gives feedback when touch the screen and responds to input for a while, then stops responding until screen comes up. I have greenify and I can confirm it does not interfere with it
Sometimes in the morning I have to even hold down the power button to reboot in order to stop the alarm
Missed few calls
List of troubleshooting methods I tried
Remove Greenify (absolutely nothing improves, standby drain increase)
Unroot (the same, nothing gets better)
Enabled ambient display (got even worse)
Clean ROM (no apps installed at all, no Google account, still the same issue)
Replaced kernel (installed insigniux and screen does take a little bit less) The eternal wait time barely happens, but is not fixed, Its a 45% fix anyway
All I ask is this is a rom bug and if it there is a workaround
Thanks in advance and have a nice day:fingers-crossed:

Did you try disabling pocket mode ?
Sent from my whyred using XDA Labs

Well I still can try it, I'm gonna see but that does not seem to be the problem

Related

Settings/Unresponsive Phone/Lock issues

Hi everyone, after hours of fiddling around with my phone and trying to figure this thing out by reading through many many forums, nothing seems to help. So out of pure frustration I decided to start a new thread (Which was my last resort)
My phone has a whole slew of problems:
First of all, I basically have no home screen. It's just a black screen accompanied by the two 'Contacts' and 'Calender" buttons on the bottom. After reading through the forums I figured it most-likely was a TouchFlo 3D issue that needs to be addressed by restarting/starting up the TL3D program. Great right? No... The damn thing won't even load when I push the Settings icon.
long story short:
-manilla.exe cpu usage is 80%-95%
-phone won't completely lock, backlight turns on with the slightest movements/bumps
-active sync wont detect phone (can't access connection settings in phone)
-phone will occasionally freeze and won't turn on unless I remove battery and restart it.
-hard reset wont work (using keystroke method, also last resort)
-lag lag lag lag lag lag ....L...A....AGGG..G
-Very low volume when engaged in a phone call (transmitting and receiving volume)
Keep in mind I can't get into settings.
Also, no new programs installed recently in case you guys were wondering.
Those are the only issues that come to mind... help??!!??!! Thank you in advance
try reflashing your rom fresh and then getting a new launcher and overclocking your min and max cpu a bit might help out

Widgetlocker Lockscreen Issue: Slider slow to respond. Help!

Hey guys,
I've been having issues with the Widgetlocker lockscreen recently, and was wondering if any of this will ring a bell with someone.
I recently flashed the KJ2 2.3.5 ROM (the XEU non-wipe Frankenstein one), and i've also flashed CF-Root and then the Speedmod kernel. I'm in the UK, on O2 (debranded to XEU) and i have no issues with the phone whatsoever. I even get great battery life. It's just this damn widgetlocker issue that's grating on me!
For some reason when i wake the phone up and try to unlock it by using the slider (i just use the default 'Android' one for unlocking - the only other things i have are a couple of widgets for missed calls & texts and a battery % one) a lot of the time the slider does not repond to touch. It doesn't always happen, but maybe a good one out of every three times it happens. And the weird part is, if i then just wait about 5 seconds, then it suddenly responds and i can unlock the phone. Obviously having another 5 seconds on top of the already present lag when pressing the home button is not good, and because of this i'm thinking of not using WL anymore.
I've been through all of the settings, i'm almost 100% sure it's not something in there. Can anyone help with this?
Cheers guys.
Happens with me too sometimes. Another issue is if you keep pressing Menu button 4-5 times the phone gets unlocked and takes you to the home screen.
Hey, just wanted to post that i finally figured out what the problem was.
I'm using an .apk to help with the touchscreen sensitivity. See vitalij's thread here:
http://forum.xda-developers.com/showthread.php?p=18999801#post18999801
Well it turns out on 2.3.5 vitalij's .apk has some issues with the most up-to-date superuser. The solution, so far, isn't great but gets the job done, is to uninstall the .apk, and then re-install. The important part is not to click on 'enable service' in the app! So basically each time you want to use the app you have to open it and hit 'apply' on whatever setting you need. The setting will work until you next turn the screen off. For me this workaround is actually ok, as the only time i ever really used it was for the odd game, so i'm happy to just do it manually on these occassions.
disable root helper
madrano, can you expand on what you mean by this? i have tried enabling & disabling root helper but if i remember correctly the problem was still there.

Phone restarts when camera flash is turned on!

Hello,
I've had my T-mobile SGH-T989 since March 2012. As it came with the standard Samsung Touchwiz loaded Android, I decided to flash a custom rom: Paranoid Android 4.4 RC2 (Android version 4.4.3), sometime back.
Ever since I have installed this new ROM everything except two things run very nicely.
1. I can use my camera, but only without any flash. The moment, I turn on the flash or put it on auto mode, the phone simply restarts. After restart, I can open the camera app, but the moment I try to take a picture with the flash on, it restarts. If I turn off the flash, the camera works without any problems.
2. Every time I am on a call, with me holding the phone to my ear (so that the proximity sensor detects that and turns off the screen to prevent accidental button press), after about 2 mins, somehow Google now gets triggered off and starts doing something on the screen (e..g opening browser, showing search history ,etc..) all the while I am talking on the phone. Off lately, approx since a week now, in addition to Google Now doing funky things, my phone now automatically goes to loudspeaker mode (even while I am holding the phone to my ear), and puts the phone on mute (although mute icon is not activated), but the other person can't hear anything.
It's just frustrating that I cannot talk without worrying about Google now triggering something off, or the phone going on loudspeaker and muting me off.
Can you guys please help resolve these issues? It's really annoying that a clean ROM like Paranoid Android is plagued with these problems, and I haven't been able to find an answer anywhere online.
Your help would be very much appreciated.
Regards,
Chintan.
Please help!
Hello Gurus,
I would really appreciate if someone can help me find out what the problem is with this phone.

Note 4 Suddenly Having a Multitude of problems. Hardware Issue?

Hello, I have had my Note 4 for quite some time now and have not had any issues with it up until the last month or so.
At first it started out as just a hiccup every now and then, an example would be when I play music via bluetooth to my Jeep CD Player, I would sometimes have to turn bluetooth off then back on to get it to connect or reconnect.
Now things are getting out of hand. Here is a list of problems I have on a daily/hourly basis and seemingly at random times. I cannot reproduce any of these problems (except the NFC problem) on demand.
I have noticed that rebooting the phone will clear up these issues (except NFC) for a short time, SOMETIMES. Other times a reboot does nothing to help the situation.
Keyboard Lag
Sometimes when I press the keys the phone vibrates indicating a key press and magnifies the key that is being pressed, but fails to enter anything in the text box/input field. For the record I am using Swiftkey. I have noticed that this happens most often when I open an app via "popup notification." For example, if I were to receive an IM or SMS I would tap on the notification that pops up, which then switches to/opens the corresponding app. It is then I will more often than not have this issue. To remedy this I have to close and re-open the app, sometimes several times causing the keyboard to open and close, several times... Sometimes when I TAP a key, the phone will behave as though I have held the key down or performed a "long press." This issue is not exclusive to the keyboard, it often happens anywhere on the screen and with any app, usually indicating that I have been "long pressing" for about 1-2sec at a time.
NFC Does Not Work
One day while I was at work I attempted to add the office printer via NFC. To my surprise I was unable to turn on NFC via the "quick settings" drawer. In the quick settings panel the NFC icon would light up, as if it were turning on, and then just turn right back off again, this happens consistently. I went into setting to enable NFC that way and I am stuck with a slider that is actually in the "on" position but greyed out, I am unable to interact with it.
Bluetooth Connectivity
I have a JVC CD player in my Jeep, I often use YouTube or Google Play Music when I drive. Usually I do not have any problems connecting to the CD player at first, but after about 30-60sec of playback the audio goes blank. The app says that it is still playing however no audio can be heard. Then it will suddenly come back on after about 5-10sec, and here is where it gets strange. After the audio comes back on after this "hiccup" the playback is fast, as in it is playing at 2X's it's normal speed, makes the vocals sound like chipmunks. This will continue indefinitely until I turn on the screen, unlock the phone, then shut the screen off. Then the audio goes on playing fine. This happens with both YouTube and Play Music, while using YouTube the video gets sped up as well. I also experience issues with connectivity where sometimes at random the phone will just disconnect from the CD player, and refuse to reconnect until I have rebooted the phone, or if it does reconnect I get no audio until the phone is rebooted. I notice that this ONLY happens when connected via bluetooth. If I turn bluetooth off while this is happening music will play over the phone's speaker perfectly normal. My CD player has a hands free feature, and I do not seem to have any issues with phone calls, it's only with music playback do I have problems.
Originally I thought it was my CD player acting up, however in light of the other problems, and the fact that I tested it with my tablet and two of my friend's phones without issue, I don't think the CD player is the problem.
Sluggish/Glitchy UI
Sometimes when the phone really freaks out, the UI behaves very strangely. Sometimes notification Icons will hover above the running app, other times the whole screen will lock in place for a few seconds. Sometimes if the screen is locked up, I will shut it off, then turn it on, shut it off, turn it on. However as I press the power button to turn the screen on and off, nothing is happening, the screen just stays black while the "back" and "recent apps" buttons light up at the bottom. Then when the screen does finally come back in it will flash on and off quickly in accordance with how many times I pressed the power button. While all this is happening, if I hold the power button to turn the phone off, the power/reboot menu will appear without incident. Sometimes when I am swiping to unlock the phone, it does not register the full swipe. Basically it acts/appears as though I lightly touched the screen and moved my finger a half inch even though I have drug my finger all the way across the screen. To remedy that issue I have to SLOWLY drag my finger across the screen and then it unlocks without incident. I have also noticed that when I go to "swipe away" a notification, especially one that has "information" in it, it will swipe off the information but leave the notification there and display the app name the notification was from. An example would be, if I just installed an app (for example YouTube) from the Play Store, the notification will say "YouTube has been successfully installed." When I swipe either left or right to remove that notification, a "white ghost box" or "overlaying top layer" with the "successfully installed" text in it will slide away. However it leaves behind a green box/notification that says "Google Play Store" and that remains until I shut the screen off and turn it back on.
NFC Will Not Turn On
I simply cannot get NFC to turn on, the slider is in the ON position but is greyed out as I mentioned earlier. I would post a picture but I guess there is a 10post rule before I can do that. I have given up on NFC, mostly because I rarely use it, so it's really not that big of a deal.
Initializing the Camera
I use an app called "Telegram" instead of SMS messaging, thus I use Telegram to share pictures with friends. Sometimes, again I am not able to reproduce this problem on demand, the problem comes and goes seemingly at random. The camera will take more than 30-60sec to initialize, while I am waiting for it I am stuck with a black screen. If the camera doesn't initialize, shutting the screen on then off will take me back to the telegram app. I never get an error message or anything. Other times when I try to use the camera it pops on instantly and works flawlessly. Originally I thought this was a problem specific to telegram, however in the name of science I tested it with the default camera app and get the same results.
USB File Transfers
I'm not really sure this is specific to my phone, but whenever I transfer files from my PC to the phone or from the phone to PC, it is PAINFULLY slow. It's even painfully slow when the PC just displays what is in the folder. However I can't say for sure this is related because I never attempted to transfer files until I started having these issues, at which point I thought it would be a good idea to start backing things up.
Gets Stuck in 3G Mode
This happens rarely, not even sure that it's related but I felt that it was worth mention.
What have I done to try to remedy this problem you ask?
So far I have performed a non-root ADB nandroid backup, just in case factory resetting the phone didn't work.
I have factory reset the phone 2 times, I see no improvements.
I have cleared out my SD card/removed SD card
I removed and/or shut off bloatware apps (Yes I tested the phone without removing/disabling bloatware, still having the same issues)
Wiped cache via Recovery
I am not sure what else I can really do to fix the phone, I am starting to think that this is a hardware issue. I should mention that there was no significant event that I feel would cause these malfunctions. System update installed and worked perfectly up until this last month, I have not dropped the phone from significant height, the phone has an otterbox anyway. I have not gotten the phone wet, it has not been left outside, this phone has not seen any abuse what-so-ever. I just started having these problems out of the blue and they seem to be getting progressively more frequent and longer lasting. If I don't get any ideas from here I am going to try to get Verizon to replace the phone via insurance, however I don't have high hopes for that because I have grandfathered unlimited data and this is not the "original" phone that I had when I added the insurance option, so I am not sure it's covered.
Does anyone have any ideas on what could be causing this or anything I can do to correct it or try to troubleshoot it?
Any help is greatly appreciated!
Phone Information is as follows:
Samsung Galaxy Note4
Model: SM-N910V
Android Ver: 5.0.1
Baseband Ver: N910VVRU2BOG5
Build#: LRX22C.N910VVRU2BOG5
HW Ver: N910V.05
Verizon Wireless
Non-Root, Default Launcher, Not modified in any way.
I realize that this is a long post but whenever I ask for help I like to be detailed. If I left out any information that might be helpful please let me know.
Unfortunately, it looks very much like components on your logic board are going bad. Sometimes a few specific things will go bad that don't actually make the phone unusable, but make it act similar to what you are explaining. It wouldn't be worth the money you'd have to pay someone to track down the bad components and replace them. If you really like the note 4, I would just make a full backup with kies while you can, buy a new phone and restore your backup.
All of Kies backups do NOT restore to a new phone! Only contacts, messages and call logs will restore on a new phone. Use Samsung Smart Switch or Helium. Good luck
Sent from my SM-N910V using Tapatalk
outcasted2003 said:
All of Kies backups do NOT restore to a new phone! Only contacts, messages and call logs will restore on a new phone. Use Samsung Smart Switch or Helium. Good luck
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
I see. I didn't know that because I've always restored my backups to the same phone. Thanks for the info.

Unresponsive display

I've gotten this problem since 20 days ago where my Google Maps get frozen in the middle of my trip. And I had reboot the device multiple times (4-5 times, sometimes skipping the LineageOS booting animation).
After fiddling over 2 weeks, I finally switched to LineageOS 17.0 now (previously using 15.1). The problem still persists.
The problem is : the screen froze, I seem able to tap something on screen but the display doesn't change anything despite my interaction with screen. This especially pronounced when I stop my screen interaction (i.e. not scrolling) on these apps
- Google chrome (say, reading any articles on web)
- Quora (especially when I about to scroll down on author bio)
- Google Sheets
- Maps
but this unresponsiveness doesn't appear at all when I:
- Play any kind of games
- watching YouTube (with the app)
In general, it seems anything that uses webview can cause the screen freezes if I leave it couple seconds. At first I thought changing from android webview to chrome webview implementation changes this. It doesn't.
The "cure" I found is simply turning the display off for 40 seconds ~ 75 seconds, and turning it back on, where I can interact with lock screen fine again. Any time lower than 40 seconds will simply show the frozen display again the time I turn the screen on.
Is it possible it's a hardware problem? (faulty RAM/storage) after using this for 2.5 years) Since full system wipe and re-install doesn't entirely solve the problem. The first time I encountered this is when I navigate with my Google Maps and the screen simply froze out during drive, and I had to restart the device multiple times, worrying that my device is broken. The next time I drive, I leave it only on Ambient Display and it didn't freeze at all.
So... any idea how to troubleshoot this?
It seems the problem is more severe than just Android.
Because even in TWRP, I noticed the display need to wait ~1 minute from the last time I turn off the display (push the power button) to reactivating it.
If I try to turn it on, the display will give black color, but I still can actually interact with the system.
ArcOnFire said:
I've gotten this problem since 20 days ago where my Google Maps get frozen in the middle of my trip. And I had reboot the device multiple times (4-5 times, sometimes skipping the LineageOS booting animation).
After fiddling over 2 weeks, I finally switched to LineageOS 17.0 now (previously using 15.1). The problem still persists.
The problem is : the screen froze, I seem able to tap something on screen but the display doesn't change anything despite my interaction with screen. This especially pronounced when I stop my screen interaction (i.e. not scrolling) on these apps
- Google chrome (say, reading any articles on web)
- Quora (especially when I about to scroll down on author bio)
- Google Sheets
- Maps
but this unresponsiveness doesn't appear at all when I:
- Play any kind of games
- watching YouTube (with the app)
In general, it seems anything that uses webview can cause the screen freezes if I leave it couple seconds. At first I thought changing from android webview to chrome webview implementation changes this. It doesn't.
The "cure" I found is simply turning the display off for 40 seconds ~ 75 seconds, and turning it back on, where I can interact with lock screen fine again. Any time lower than 40 seconds will simply show the frozen display again the time I turn the screen on.
Is it possible it's a hardware problem? (faulty RAM/storage) after using this for 2.5 years) Since full system wipe and re-install doesn't entirely solve the problem. The first time I encountered this is when I navigate with my Google Maps and the screen simply froze out during drive, and I had to restart the device multiple times, worrying that my device is broken. The next time I drive, I leave it only on Ambient Display and it didn't freeze at all.
So... any idea how to troubleshoot this?
Click to expand...
Click to collapse
Can you enable "Show Tap" option in developer settings and see if theres any ghost touch happening, sometimes ghost touch can "freeze" the screen while you want to interact with it
Shimizux said:
Can you enable "Show Tap" option in developer settings and see if theres any ghost touch happening, sometimes ghost touch can "freeze" the screen while you want to interact with it
Click to expand...
Click to collapse
Thanks for responding.
I already enable "Show taps" on developer options. But the problem is that the screen freeze happened when there was no touch at all (i.e. I just looking at the screen, reading)
There's new observation I made today that : usually the screen doesn't want to immediately awaken when I just turn the screen off.
Today I tried to remove fingerprint from lock screen, the screen now is able to respond quickly again upon pressing power on button. It's still as responsive to power on when I add pattern to the device lock mechanism.
I'm not too sure whether this is OS level problem or even closer to hardware problem because this kind of unresponsiveness is also apparent even when I boot to TWRP.
ArcOnFire said:
Thanks for responding.
I already enable "Show taps" on developer options. But the problem is that the screen freeze happened when there was no touch at all (i.e. I just looking at the screen, reading)
There's new observation I made today that : usually the screen doesn't want to immediately awaken when I just turn the screen off.
Today I tried to remove fingerprint from lock screen, the screen now is able to respond quickly again upon pressing power on button. It's still as responsive to power on when I add pattern to the device lock mechanism.
I'm not too sure whether this is OS level problem or even closer to hardware problem because this kind of unresponsiveness is also apparent even when I boot to TWRP.
Click to expand...
Click to collapse
That is one big weird problem, i've never encounter something like that since i ever using a smartphones.
It does really sound like, it just a software problem. But if it also happen in TWRP, it doesn't look like it.
I also have installed LOS17 by Arian before too, and i dont have that problem.
Sorry man i have no idea nor expert about it
It could be your battery is dying?, if your battery cant give enough power to the screen already, screen gonna act like crazy i.e ghost touch etc.
I have a broken battery been using it for 2Year + because of the battery my screen has a problem too. I replaced it last december 2019 and everything went normal again.
Shimizux said:
That is one big weird problem, i've never encounter something like that since i ever using a smartphones.
It does really sound like, it just a software problem. But if it also happen in TWRP, it doesn't look like it.
I also have installed LOS17 by Arian before too, and i dont have that problem.
Sorry man i have no idea nor expert about it
It could be your battery is dying?, if your battery cant give enough power to the screen already, screen gonna act like crazy i.e ghost touch etc.
I have a broken battery been using it for 2Year + because of the battery my screen has a problem too. I replaced it last december 2019 and everything went normal again.
Click to expand...
Click to collapse
I don't think it's a battery problem. I see that I can play game for 1hr+ fine. A game that require exact timing of 2 touches on top of that. So that ghost touch really doesn't appear.
But yeah, it's really 2 contrasting sign
- In one hand, it seems an OS problem because I can simulate an environment where the screen definitely won't be frozen for hours, while on specific other environment, the screen freeze can happen very quickly between release and re-occurence.
- On the other hand, the problem seem doesn't stop on OS level because it can be found in TWRP.
If I read an answer on Quora that shows GIF image on the section I read, the screen freeze 100% won't happen. I tried the same thing on imgur too, the screen freeze won't happen.
So it seems that as long as the screen is showing dynamic content, it won't freeze (that's why game and YouTube doesn't show this kind of problem, but reading a web full of text/static images can)
A bit of update : I have left my phone in off state for 4-5 days. And I have been using it again, albeit, less extensively since my main phone has changed to K20 Pro.
Long story short : I haven't encountered screen freeze again. But this is just after 2 days playing with less intensity.
I wonder what really went wrong.

Categories

Resources