Database Users

Wake Lag?

I've noticed this problem from the day I got my phone (10/10/13). I'll experience a full second or more of lag when trying to wake the phone by hitting the home button or the power button.
It's pretty bad, so much so that I sometimes think I may have missed the button and go for it again.
Is this common? I've searched online and I haven't found anything about the Note 3 but I see stuff about it happening on the previous Note.

One thing u can try that made speed things up slightly is to go into developers options and turn off or change the transition animation scale, Window animation scale and Duration animation scale. It won't brake anything and it just may help a little. The default setting for each is a 1 so I'd either change em all to a 0.5 or turn em to off. And hell, if u don't think it helps you can always change em back. Worth a shot at least.
Sent from my SM-N900V using Tapatalk

Ibkevin said:
One thing u can try that made speed things up slightly is to go into developers options and turn off or change the transition animation scale, Window animation scale and Duration animation scale. It won't brake anything and it just may help a little. The default setting for each is a 1 so I'd either change em all to a 0.5 or turn em to off. And hell, if u don't think it helps you can always change em back. Worth a shot at least.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Nice tip. In all my years of Android tweaking, I've never come across that one. I don't need fancy screen on/off animations. I prefer quicker response time. Thanks.

This phone is fast enough to where you should be able to do screen on animation with no lag. I'd try wiping cache before disabling anything
Sent from my SM-N900V using xda app-developers app

noticed too
sintricate said:
I've noticed this problem from the day I got my phone (10/10/13). I'll experience a full second or more of lag when trying to wake the phone by hitting the home button or the power button.
It's pretty bad, so much so that I sometimes think I may have missed the button and go for it again.
Is this common? I've searched online and I haven't found anything about the Note 3 but I see stuff about it happening on the previous Note.
Click to expand...
Click to collapse
I have noticed this too... bugs the hell out of me. i tried putting animations to .5 cause i think it makes the phone look like crap when set to 0, helped a little bit but it is still there.

I noticed this last night. I was missing the swipe to unlock because it was taking so long. Seems ok now, though.

I found a slightly faster response with the three animation options set to 0.

I think its a touchwiz thing my s4 did it stock and it went away with Hyperdrive rom but it came back when I was on cynanogen mod. I feel like my I wore out my power button lol it is a little loose.
Sent from my SCH-I545 using xda app-developers app

Its a Samsung thing with the processor. The Note 2 was the same way. The easiest way explained to me awhile back....once your screen goes off...and all stuff running finishes up...you essentially enter Deep Sleep. It's a battery saving feature...if you will.
Manually turn off your screen, then like..2 seconds later, turn it back on. Should be virtually instant. Now do the same thing but wait 2 minutes....lag.
It is 'kind of' annoying, but I'll deal with it for the sake of battery life.
Now that we have root, you can always try to adjust governors and kernel settings to help it, but until we're able to use other kernels, it's gonna pretty much always be there, the lag, that is.
Hope that helps explain a bit.

The only way around it on the Note 2 was to force a wake lock, basically it never enters deep sleep. You may be able to use an app to do it as well, such as: https://play.google.com/store/apps/details?id=eu.thedarken.wl
MikeyXDA was an advocate of the method and explained it really well on his MeanBean ROM for the Verizon Note 2. You just take a slight hit to battery, but at least there's no wake lag.
Here's the thread: http://forum.xda-developers.com/showthread.php?p=543135
Sent from my SCH-I605 using XDA Premium 4 mobile app

I have absolutely no wake lag on mine at all. I was expecting it like my Note 2 but I hit the button now and it's just on instantly.

Wake lag with sd card
sintricate said:
I've noticed this problem from the day I got my phone (10/10/13). I'll experience a full second or more of lag when trying to wake the phone by hitting the home button or the power button.
It's pretty bad, so much so that I sometimes think I may have missed the button and go for it again.
Is this common? I've searched online and I haven't found anything about the Note 3 but I see stuff about it happening on the previous Note.
Click to expand...
Click to collapse
I'm having a problem with wake lag bad sometimes - several seconds. Mine seems to be connected to the sd card. I have a 32 gb card I used in my note 2 with no problem, it's and sdhc i think. I cleaned it down to 8g of stuff on it and put it in. It kept causing note 3 to dis mount the card each time I turned it on; had a little message at the top left. Much of the time the card would stay dismounted. When I finished a call the screen would not come back on for a long time, couldn't end the call. Took the sd card out, problem resolved. Backed up the sd card, put it in the N3 and formatted. Got better results although still doing it some. I'm wondering if I'm going to have to get a new sd card or trade in for a new note 3.
Any thoughts. I would check the sd card if you still see long lags.

Try to freeze/remove S Voice if you rooted because S Voice is mapped to double tapping the home button. This helped me out a lot on the Note 2 and I removed it already on the Note 3 without comparing lag difference already

Touchscreen sensitivity

Been using the 2nd gen Moto G for a week and I've noticed the touch screen isn't as sensitive/accurate as my previous phone (NEXUS 4). For example, when I scroll (in Facebook, Chrome etc.), the app opens links and images if my thumb is over either one. It's the same with gallery. If I were to scroll then halt, it'll open the image under my thumb. It's doesn't happen often, but enough to take notice. I have to press slightly harder (compared the NEXUS 4) for the Moto's touch screen to register accurately. Can't use light touches reliably at all. Has anyone experienced similar/same issue?

Not an issue with me like this
Works fine

It is by no means bad, but it takes a little bit of getting used to. I'm guessing they'll fix it via OTA if it needs fixing.

I have noticed the same thing. I am also coming from nexus 4. I find these touch issues very irritating. Overall scrolling isn't as smooth as the n4 as well. I think scrolling could be related to the kernel configuration.

anshumandash said:
I have noticed the same thing. I am also coming from nexus 4. I find these touch issues very irritating. Overall scrolling isn't as smooth as the n4 as well. I think scrolling could be related to the kernel configuration.
Click to expand...
Click to collapse
Glad I ain't the only one. Hopefully it is software related and can be addressed via update

I have this only when I charge my phone with a specific wall adapter, everything else is fine

Gabboplano said:
I have this only when I charge my phone with a specific wall adapter, everything else is fine
Click to expand...
Click to collapse
Strange, I didn't notice this issue before yesterday's OTA.
Will try other another wall adapter.
I'm currently using the Sony/Ericsson LwW adapter (5V/800mA).

My Moto G 2nd Gen had this issue too, but it also had problems where occasionally the touch screen would interpret scrolling as tapping and vice versa, in the end, I had to RMA it.

I had mentioned earlier that sometime scrolling would consider as tapping and would open apps/links etc. Some time tapping needed multiple taps. I just removed the screen guard and this problem is mostly not noticeable any more. Just thought this information might help some one.
My phone came with the official charger of 550 MA and I don't get any screen freezing while the phone is charging with it.

Okay, i had this problem too. However i got the phone replaced so now i'm using a different handset and the issue is resolved for me. At first even i thought that this is the problem related to the software but i started to notice this over and over again. So i spoke to flipkart and they agreed to replace the handset. So i suggest to all the people who are having this problem to get your phone replaced.
Sent from my Nexus 5

sahil kaul said:
Okay, i had this problem too. However i got the phone replaced so now i'm using a different handset and the issue is resolved for me. At first even i thought that this is the problem related to the software but i started to notice this over and over again. So i spoke to flipkart and they agreed to replace the handset. So i suggest to all the people who are having this problem to get your phone replaced.
Sent from my Nexus 5
Click to expand...
Click to collapse
Did you have the problem even without a screen guard? After I removed the screen guard, I get this tap while scrolling may be only once a day. Normal sensitivity is far better without a screen guard.

anshumandash said:
Did you have the problem even without a screen guard? After I removed the screen guard, I get this tap while scrolling may be only once a day. Normal sensitivity is far better without a screen guard.
Click to expand...
Click to collapse
As soon as i got the phone, i booted it up with the screen guard on that's when i first realise that there is a problem with the scrolling and tapping on the touch screen. I removed the screen guard immediately and even after that the scrolling was mistaken for tapping. Used it for a few days and still had the issue. It did not happen very often if I compare it with the screen on time, but it was enough for me to be pissed at. I would rate it at about 30 % of the time when im scrolling, sometimes in a music playlist or when i am browsing or scrolling just about anything.
Sent from my Nexus 5

sahil kaul said:
As soon as i got the phone, i booted it up with the screen guard on that's when i first realise that there is a problem with the scrolling and tapping on the touch screen. I removed the screen guard immediately and even after that the scrolling was mistaken for tapping. Used it for a few days and still had the issue. It did not happen very often if I compare it with the screen on time, but it was enough for me to be pissed at. I would rate it at about 30 % of the time when im scrolling, sometimes in a music playlist or when i am browsing or scrolling just about anything.
Sent from my Nexus 5
Click to expand...
Click to collapse
I have another question. In the new phone do you see any stuttering or jitter while scrolling through apps. It harkens to me in many apps even on g+, scrolling through contacts, Facebook, Tapatalk etc. I know this could be software related. But just wanted to check with you. Now the tapping during scrolling issue happens really less, but it happens if the scrolling is jittery.

delete please

anshumandash said:
I have another question. In the new phone do you see any stuttering or jitter while scrolling through apps. It harkens to me in many apps even on g+, scrolling through contacts, Facebook, Tapatalk etc. I know this could be software related. But just wanted to check with you. Now the tapping during scrolling issue happens really less, but it happens if the scrolling is jittery.
Click to expand...
Click to collapse
I have a feeling that is also to blame. I've noticed it when using FB, Chrome etc.
The surface of the glass may also be one of the culprits. My thumb and fingers don't glide as well on the Moto compared to my NEXUS 4. Sometimes I have to apply bit more pressure to keep my thumb firmly on the screen. Otherwise I can feel it loosing contact. It's very obvious after cleaning the screen with soft cloth. Maybe it is to do with the coating? I've ran touch screen tests and the screen detects inputs just fine. I don't see the point of returning mine, cos they won't find anything wrong with it.
PS: Android L should drastically reduce or eliminate stutters (and lag) thanks to Android Run Time (ART). People are already seeing major improvements, but I don't recommend enabling it in KitKat. It's can screw up your phone and apps. But if you wanna take the risk, click on ART Under "Select Runtime" option in developer options.

touch sensitivity
this problem appeared once, after an update from motorola.
Factory resetting it solved the problem xd

Nielo TM said:
I have a feeling that is also to blame. I've noticed it when using FB, Chrome etc.
The surface of the glass may also be one of the culprits. My thumb and fingers don't glide as well on the Moto compared to my NEXUS 4. Sometimes I have to apply bit more pressure to keep my thumb firmly on the screen. Otherwise I can feel it loosing contact. It's very obvious after cleaning the screen with soft cloth. Maybe it is to do with the coating? I've ran touch screen tests and the screen detects inputs just fine. I don't see the point of returning mine, cos they won't find anything wrong with it.
PS: Android L should drastically reduce or eliminate stutters (and lag) thanks to Android Run Time (ART). People are already seeing major improvements, but I don't recommend enabling it in KitKat. It's can screw up your phone and apps. But if you wanna take the risk, click on ART Under "Select Runtime" option in developer options.
Click to expand...
Click to collapse
I completely agree with you. This phone has got two coatings. One called splash resistant and the the other is finger print resistant coating. I think those are another cause the finger doesn't glide well on the screen. I am also coming from Nexus 4 and I can feel this problem every time as I still carry the N4 with me. I too ran touch screen tests and everything looks fine. I am not sure if I RMA how will the 2nd device behave. It might be same. I can actually replace it from Flipkart.com from where I bought, but I am not sure if that will help.
I read some review comparison between the new moto g and new moto x and the reviewer has commented that Moto x 2014 screen is far more responsive than the moto g 2014. I know the problem was real bad with the stock screen guard on the screen. If I need to manage with the phone, I know I will have to use the phone without a screen guard.
I tried using ART as I have been using that on my N4 since Jan 2014. But in Moto g the app optimization starts at every boot with ART taking more than 10 mins for every boot. I wrote a mail to Moto support and they said there is a technical problem with the builds and they suggested me to use Dalvik. I think they won't fix it till Android L drops in.

DoubleTap to Lock/Wake while using Apex Launcher

My apologies if this is a repeat post.
It has been mentioned before that the double-tap-to-wake does not working with anything but the stock launcher. Actually technically the *wake* should work with any launcher. I just installed Apex (my regular launcher), and it is still working just fine. What does not work is the *lock*. Apex has its own double-tap gesture definition, and lock isn't one of the options. So to get around that, you can go to the Play Store and download, install and activate "Screen Off and Lock" . One option on the Apex double-tap setting is to launch any other app. You can now configure it to launch this app. Once you do that, when you double tap while in Apex, it will lock the screen. When you double tap again, it will unlock ( I do not think that has anything to do with Apex anyway ) .
Apex is my favorite launcher and I have been looking for a way to get back to it without losing the double tap. Now I can change themes, make my drawer look better and set up many other gestures. Hopefully this trick can work in any other launcher you want to use. And at the minimum , the double tap to wake should work regardless.

Double tap to wake works for me with Google Now launcher and Nova (free version). Double tap to sleep (lock) doesn't work with either. Works fine both ways with the stock Idol launcher. Looks like you may have discovered a work around.

stl1859 said:
My apologies if this is a repeat post.
It has been mentioned before that the double-tap-to-wake does not working with anything but the stock launcher. Actually technically the *wake* should work with any launcher. I just installed Apex (my regular launcher), and it is still working just fine. What does not work is the *lock*. Apex has its own double-tap gesture definition, and lock isn't one of the options. So to get around that, you can go to the Play Store and download, install and activate "Screen Off and Lock" . One option on the Apex double-tap setting is to launch any other app. You can now configure it to launch this app. Once you do that, when you double tap while in Apex, it will lock the screen. When you double tap again, it will unlock ( I do not think that has anything to do with Apex anyway ) .
Apex is my favorite launcher and I have been looking for a way to get back to it without losing the double tap. Now I can change themes, make my drawer look better and set up many other gestures. Hopefully this trick can work in any other launcher you want to use. And at the minimum , the double tap to wake should work regardless.
Click to expand...
Click to collapse
Nova Launcher has an identical gesture/setup. [ which I'm using in same way with the "Screen Off" app since the phone auto locks when the screen goes blank. ]

I have experienced the inconsistency with dt2w. I kept deactivating/activating it and it's been working adequately (~60% of the time, still sucky but much better than before). Like others have said, it works much better if the phone is sitting on a desk as opposed to attempting it while in your hand. I really hope the reliability of dt2w gets improved in the next OTA update.
Using Nova and a double tap gesture that activates a screen lock app works perfectly for me.

JJ2525 said:
I have experienced the inconsistency with dt2w. I kept deactivating/activating it and it's been working adequately (~60% of the time, still sucky but much better than before). Like others have said, it works much better if the phone is sitting on a desk as opposed to attempting it while in your hand. I really hope the reliability of dt2w gets improved in the next OTA update.
Using Nova and a double tap gesture that activates a screen lock app works perfectly for me.
Click to expand...
Click to collapse
Same here, NOVA launcher premium

My dt2w works flawlessly to turn screen off. It only works 50% of the time to get it on.

maddog497 said:
My dt2w works flawlessly to turn screen off. It only works 50% of the time to get it on.
Click to expand...
Click to collapse
Exactly the same situation here.

Borghi said:
Exactly the same situation here.
Click to expand...
Click to collapse
I'm spoiled with the G3 and the Zenfone 2. They both work flawlessly.
Hopefully this gets fixed in an update.
Sent from my LG-D852 using Tapatalk

Thank you very much dude, I'm hoping to root ASAP still haven't found a reliable way to. I wish this device had a bit more ram but pretty good so far. I hate not being rooted just because I can erase anything on the external SD and hopefully with a custom Tom the screen Issues with the phone not waking gets fixed

You don't have to be rooted to delete files on the external drive. There's a thread here that covers that. I'll post the link when I'm on the PC.
Sent from my Alcatel OneTouch Idol 3 using Tapatalk

Shodan5150 said:
You don't have to be rooted to delete files on the external drive. There's a thread here that covers that. I'll post the link when I'm on the PC.
Sent from my Alcatel OneTouch Idol 3 using Tapatalk
Click to expand...
Click to collapse
Sorry it took so long fopr me to get back here to post the link. I had PC issues and had to install Windows and then the hardware drivers for the AMD card gave me a fight. But you prolly already found the thread but the thread is below.
http://forum.xda-developers.com/idol-3/help/install-to-sd-card-root-access-t3119374

New discovery
Some of you may have already discovered this - but this is certainly new for me. What I am noticing about the double-tap-to-wake - is that it always works - BUT - what is happening is that often it is slow - and I mean really really slow sometimes. Most of us would perceive that as not working - and try it again. And double-tap, on top of double-tap just makes matters worse. What I did was - tried double-tapping once - and when the screen did not come back on, just let it be for about 10+ ( probably more than that at times ) seconds - and it eventually came back on. Even under normal circumstances, the screen wakeup is slow . It looks like sometimes it just takes forever, creating the impression that it is not working. I am not trying to suggest that we can say that this behavior qualifies as 'working' - but at least we know what exactly the problem is.
I hope Alcatel pushes a fix for this. Till that time - I will have to continue to rely on single-tap to wake ( aka the power button ) if double tap to wake does not work.

stl1859 said:
Some of you may have already discovered this - but this is certainly new for me. What I am noticing about the double-tap-to-wake - is that it always works - BUT - what is happening is that often it is slow - and I mean really really slow sometimes. Most of us would perceive that as not working - and try it again. And double-tap, on top of double-tap just makes matters worse. What I did was - tried double-tapping once - and when the screen did not come back on, just let it be for about 10+ ( probably more than that at times ) seconds - and it eventually came back on. Even under normal circumstances, the screen wakeup is slow . It looks like sometimes it just takes forever, creating the impression that it is not working. I am not trying to suggest that we can say that this behavior qualifies as 'working' - but at least we know what exactly the problem is.
I hope Alcatel pushes a fix for this. Till that time - I will have to continue to rely on single-tap to wake ( aka the power button ) if double tap to wake does not work.
Click to expand...
Click to collapse
I have tried waiting for the screen without it coming on. Putting it on the desk and trying it and leaving it there, with no response. After a reset or disabling then enabling the function would work for a brief while. After that nothing seemed to help. If I used the power button to activate the screen and then try the DTTW, it would work but as soon as the phone went idol, so did the DTTW. As much as I liked the phone for the most part, I was not prepared to go past my return date without even one update coming from Alcatel.

maddog497 said:
I have tried waiting for the screen without it coming on. Putting it on the desk and trying it and leaving it there, with no response. After a reset or disabling then enabling the function would work for a brief while. After that nothing seemed to help. If I used the power button to activate the screen and then try the DTTW, it would work but as soon as the phone went idol, so did the DTTW. As much as I liked the phone for the most part, I was not prepared to go past my return date without even one update coming from Alcatel.
Click to expand...
Click to collapse
Since the time I arrived at this theory, I have tested it again and again - and I can confirm that it is always doing it. You just have to be really really patient to see this in action. Forget what I said about 10 seconds ; sometimes you have to wait for more than a minute. It is weird - you double tap - then just stare at the phone for ages and suddenly out of nowhere the screen lights up.
If D2W is important for you , then my discovery does nothing for you - It is still broken. So you did the right thing in returning it. As far as updates go, again if that is important for you, then you did the right thing. Honestly I do not expect many ( if at all ) updates from TCL. From what I understand, they do not have the kind of software development infrastructure that Asus does . And that is evident from the extent of skinning that Asus did on top of Lollipop whereas the Idol3 was mostly a stock experience. IMHO - right now - more than updates from TCL, we need root , so that developers can do their own thing with the phone.

I have since installed a proximity sensor based wave-to-unlock app. Not only does it work very well, it also allows me to lock the screen back, from the lock-screen itself, something that is missing in the default D2W setup. The only downside is the additional power consumption by the proximity sensor. Since it is supposed to use only 3 mA , I am hoping it is not going to be too bad, but I will watch out for it. If the battery performance does not degrade too much, then I think I can kiss D2W goodbye.

I sent an email to Altatel Tech Support about a week ago and asked them if they are aware of the DTTW issues and working on a fix. I received a reply stating that they are aware and are working on an update. My guess is that they will try to combine multiple fixes into a single update. It may take a little longer and it is too bad that Alcatel is not better at communicating with its customers. It would make no sense for Alcatel to ignore all of the customer complaints here, on Amazon, and in various reviews and do nothing. They are spending cash marketing this phone and they must be smart enough to know that their sales will tank if they ignore the issues.

Hey guys, just thought I'd let you know of a solution that appears to fix the double tap to wake issue everyone is having. Like most of you, I've been annoyed that this only works like 50% of the time. I've noticed in the G4 forums of people having issues with their double tap to wake not working as well also (only 80% of the time, still much better than idol 3). One of their fixes is to download SGS Screen Booster from the Play Store. Using the Super Optimized preset, I can say that double tap to wake works 10 out of 10 times in my testing.
https://play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com&hl=en

japhule said:
Hey guys, just thought I'd let you know of a solution that appears to fix the double tap to wake issue everyone is having. Like most of you, I've been annoyed that this only works like 50% of the time. I've noticed in the G4 forums of people having issues with their double tap to wake not working as well also (only 80% of the time, still much better than idol 3). One of their fixes is to download SGS Screen Booster from the Play Store. Using the Super Optimized preset, I can say that double tap to wake works 10 out of 10 times in my testing.
https://play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com&hl=en
Click to expand...
Click to collapse
I tried this app and it seems to improve lag time when you open an app too! Great find!

OTA
An official OTA update has just been announced to fix the DTTW
Borghi said:
I tried this app and it seems to improve lag time when you open an app too! Great find!
Click to expand...
Click to collapse

Touch screen fix

If anyone is looking for a solution to touch screen issues where scrolls register as taps, go to settings>accessibility>motor & cognition and set Touch Feedback Time to Medium (or Long, your choice).
I factory reset my phone, and it improved a bit... but was bored and cycling through some menus and saw this. Since I changed it I haven't had a single problem.

i will give this a try today. let you know my results. I set mine on medium

On vzw its actually under dexterity and interaction. Will give it a shot and see how it goes thanks!

I'll give it a try too. Will report back. Thanks!

As of now, this seems to fix my Knock to Wake issues I've been having! BEAUTIFUL! You rock!
Did not have many touchscreen issues to report though, but I'll make sure and keep everyone posted if I notice any improvements.

Since turning it on medium in this short time I will say it is better. Knock to wake works much better but like @liamR above I did not have as severe issues as others have reported. Will report back at the end of the day again
Sent from my LG-H815 using Tapatalk

Set to long. Works fantastic. Thanks!
Sent from my LGLS991 using Tapatalk

This seems to help I think
Sent from my LG-H811 using Tapatalk

Set to long. So far, there an improvement but not perfect. Digging this little gem so far. Thanks for the find.
Sent from my LGLS991 using Tapatalk

No change for me. Tried medium and long. Still missed taps and lag.

tveith said:
No change for me. Tried medium and long. Still missed taps and lag.
Click to expand...
Click to collapse
factory reset the phone...pretty much your only option to fix. If not you may have to get a replacement

Haha I've exchanged the phone once and factory reset twice. I have tried developer options, screen booster app, etc. The missed taps aren't horrendous, but just bad enough to make me want to pull my hair out when typing an email or text. I have 1 day left to decide if I want to trade it for an s6 edge. Just know I'll miss the removable battery and sd slot. Decisions decisions.

Seemed to have helped! At least so far.
Sent from my VS986

On the Verizon Model, the location is little different, as noted:
Settings>Accessibility>Dexterity and Interaction>Touch feedback time: [Short, Medium, Long]
Just did this, so I have no response to whether there are any changes.

Thanks for the tip! Unfortunately, I haven't noticed a big difference yet, and still has a failed knock code attempt, but I'll need to give it more time to evaluate better.
At least with Verizon, however, this does seem to involve a bit of a trade-off.
When long-pressing the square button on the home screen, for instance, I need to hold it longer before I get the long-press menu. Quite a bit longer, if set to Long vs Medium, coming from Short.
This seems to apply in other apps, as well, for holding the square button. I don't notice a difference in how long I need to long-press a Google Keyboard key to get the alternate character. Long-pressing on text to select it seems to take longer.
This may be obvious to everyone else. But as I'm not sure what this setting really controls, I hadn't expected it.

I've just gone from short to medium and the one issue I had with swipes becoming taps seems to have been resolved... Cheers

Glad this is working for the most part. I've gone 2 days strong with no more scrolls registering as touches.

Factory reset originally worked for me, but will try this as well.

Set mine to medium. Completely fixed it on T-Mobile. Thanks OP!
Sent from my LG-H811 using Tapatalk

I don't know.. Impretty sure this only adjusts the time it takes for something to react on a long press.. If you set it to.medium or long it will take longer for long pressed items to react.. Could be wrong, but I think it's placebo..

gaming stutter issue?

I'm not sure if it's because I'm rooted or what, but I noticed most basic games lag really bad on my phone, like fallout shelter for instance it locks up for a few seconds every couple of seconds and it's pretty annoying... Any ideas?

KyleBryant said:
I'm not sure if it's because I'm rooted or what, but I noticed most basic games lag really bad on my phone, like fallout shelter for instance it locks up for a few seconds every couple of seconds and it's pretty annoying... Any ideas?
Click to expand...
Click to collapse
Since I've had this phone I have had some performance issues with games and apps. Some of them were very strange (Ie: certain graphics or images showing up as black boxes.) Most of these were fixed via app updates. Still having some strange issues with certain apps being cutoff at the bottom (ie Snapchat just had a black bar on the bottom which makes it hard to send a message because you cannot press the send button.) I am now a month and a half into this phone. I am experiencing lag even while scrolling through apps or switching apps. I am also experiencing strange delays with the keyboard popping up when I touch a text field. It's hit or miss. Overall I still love the phone.
Side question. How did you root?
Sent from my Moto E (4) using Tapatalk

I posted a guide to rooting here https://forum.xda-developers.com/moto-e4/how-to/moto-e-guide-to-rooting-t3652982