Touchscreen sensitivity - G 2014 General

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.

Related

[Q] Erratic Touch Behavior?

Has anyone run into issues w/touch on this device periodically?
I've been having problems with mine from time to time where a touch is registered in the wrong location... like very wrong, I notice this most often when looking through menus in the system settings.
I fight with scrolling properly in a few diff apps. One in particular is pocket informant. Some times I also have trouble switching home screens and the transition starts to twitch when it hits about half screen then ultimately returns to the screen I'm trying to move away from.
If you would like a video I can try to capture it
Is this common or should I start an RMA and get a fresh new A7 on the way?
I've had this problem sometimes. I think it's because the screen is probably low quality or something is.
Ive also noticed that if I bring it too close to my face to see the side buttons in the dark, my breath on the screen makes things jump around spastically.
eskaryo said:
Has anyone run into issues w/touch on this device periodically?
I've been having problems with mine from time to time where a touch is registered in the wrong location... like very wrong, I notice this most often when looking through menus in the system settings.
I fight with scrolling properly in a few diff apps. One in particular is pocket informant. Some times I also have trouble switching home screens and the transition starts to twitch when it hits about half screen then ultimately returns to the screen I'm trying to move away from.
If you would like a video I can try to capture it
Is this common or should I start an RMA and get a fresh new A7 on the way?
Click to expand...
Click to collapse
My screen has been touchy as well

Anyone else Got Touch Lag?

Firstly hello to all my fellow Vega UK users!
For the price I think this device is great, but it does have it's issues.
Do any of you have the problem where the touch screen just seems to stop working? It'll kick in again soon enough, but it's frustrating as hell.
Also sometimes the task manager seems to appear by itself, but I can;t get it to appear when I need it?
I'm using Pauls Add-on ROM. (thanks Paul )
Logicalstep
I havn't had any major lag at all.
What do you mean by task manager? do you mean the one when you hold "home"?
I have found after a lot of use, with a lot of apps open that the system can lag. I guess this is due to system resources. Recommend installing ES Task Manager from the market to manage running tasks.
You mentioned the task manager appears by its self, do you mean the home screen selector? I found hitting the home button to many times makes this display.
Some users have reported issues with the touch system when the tablet is charging. Do these issues only appear when plugged in?
adfrad said:
Some users have reported issues with the touch system when the tablet is charging. Do these issues only appear when plugged in?
Click to expand...
Click to collapse
Yes believe so. due to non regulated power supply causes the screen to become over sensitive.
I get this issue too occasionally, vastly increased when plugged in, now and then when not.
I dont use the machine when its charging.
No real rhyme or reason to it occouring in my experience, id love to know of a cause, other than dirty screen.
Rgds
Lok
Yeah It's a bit of a strange one tbh.
Can;t say I have noticed the lag more when plugged in. I though the PSU was regulated, isn't it just a standard Switch mode PSU?
On the task manager, well obviously there is a task manager with Foryo and oon my Galaxy s I hold the hold button down and it appears, however there doesn;t appear to be a reliable way to do this on the Vega....or am I wrong?
Logicalstep
I never get any touch lag, but I'm not convinced "lag" is the word you want.
"lag" would indicate that the response is somewhat behind the touch action. Android versions below Gingerbread do suffer from that when the CPU is loaded but the Vega is better then most in that regard.
What it does suffer from a _lot_ it erroneous and missing touch events (especially when using a poorly smoothed PSU like the one provided) symptoms include:
1. Swipe gestures being terminated before you lift your finger.
2. Long press actions acting like multiple-presses.
3. (The most common for me) Finger up events failing to register (resulting is erroneous long-presses)
But none of these are "lag". I believe there are grounding problems in the Vega and thus how you hold the tablet and the humidity and static of the environment can change the reliability of the touch screen. It's been reported that having the Vega plugged into a desktop via USB increases the reliability of the display (at least when also charging) which lends credence to the idea that it's grounding related.
What I have noticed ín particular is that holding the tablet in landscape mode makes the keyboard ultra inaccurate. You must press much below the level you want. E.g., if you want to write a Q you hit the A key. It's a bit bothersome while writing...
I haven't experienced any lag, just a slight deadzone at the bottom of the screen and inaccurate keyboard typing. Nothing major. I also haven't really noticed the messed up screen sensitivity when charging that people have been going on about.
Sent from my HTC Desire using Tapatalk
CalumD said:
I haven't experienced any lag, just a slight deadzone at the bottom of the screen and inaccurate keyboard typing. Nothing major. I also haven't really noticed the messed up screen sensitivity when charging that people have been going on about.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Try this out:
http://android.modaco.com/content/advent-vega-vega-modaco-com/327198/screen-calibration-app/
HunteronX said:
Try this out:
http://android.modaco.com/content/advent-vega-vega-modaco-com/327198/screen-calibration-app/
Click to expand...
Click to collapse
I gave if a try, seems to have made typing on the Vega a whole lot better!
Sent from my HTC Desire using Tapatalk
Confirmed over at modaco and by myself also.
Not 100pc improvement but a 90pc. Another essential app.
Goodstuff.
Rgds
Lok
Iv seen lag when I first turn it on but it goes away in couple of minutes, if its on standby it never lags.... cmon honeycomb!!!!
Sent from my HTC Desire using XDA App
The performance pack really reduces start up lag issues btw.
I've seen the device lag sometimes but since i installed pauls peformance pack the lag has gone away making the device so much better.
Well for me the keyboard is still a major issue. Not lag really, but it appears to register my touches multiple times. Right now Im typing this reply on my tablet and I have to go back so many times to correct multiple characters, spaces etc. Its just taking so long and requires so much effort to write a simple message.. for browsing and apps I love it but for email its horrible..
dopeh said:
Well for me the keyboard is still a major issue. Not lag really, but it appears to register my touches multiple times. Right now Im typing this reply on my tablet and I have to go back so many times to correct multiple characters, spaces etc. Its just taking so long and requires so much effort to write a simple message.. for browsing and apps I love it but for email its horrible..
Click to expand...
Click to collapse
Have you tried cleaning your screen and then using the calibration program posted on modaco?
zzleezz said:
Have you tried cleaning your screen and then using the calibration program posted on modaco?
Click to expand...
Click to collapse
Just tried it but doesn't seem to make any difference..
dopeh said:
Just tried it but doesn't seem to make any difference..
Click to expand...
Click to collapse
OK just to be sure...
Is the power supply plugged in? (Screws up the calibration in my experience)
Are you touching the screen while it calibrates?

How do I test for true missed touches?

OK, so here's my problem. I recently returned my nexus 7 for a newer production date build because I had a horrible touch screen. I updated the new one and had missed touches/sticky keys but when I unlocked it to apply sfhub's fix it wiped everything and the problem is gone (maybe a bad upgrade install?) Every once in awhile it feels like it's still missing a touch. Like once every couple hours. I've noticed that the touch screen is very sensitive and if I move my finger a little bit while touching it registers as a swipe I guess. Is there a way to see if it's really not seeing the touch or registering as something different? There are no sticky keys whatsoever and multi-touch seems to work fine in a case or out. Does anyone else see this with theirs?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Enable developer options and see the touches
You can test/verify the touches by enabling the developer options on the Nexus.
To do this, go to settings, go down to "About tablet", and then down again to the build number. Tap the build number information ca. 5 times (5 to 10? after a few taps you will see an info sign about how many times you still have to tap), this enables the developer mode.
In the settings menu there should be now a new item, Developer options (just before the About tablet). In the developer options check the box named "Pointer location".
Now when you touch the screen, with one or more fingers, you can see a screen overlay with coordinates and axles showing where the device sees your touches.
I have the touchscreen problem with missing and sticky touches and pinch and twist problems, the whole menu. For example, using google maps or writing emails is a pain in the ass because of these touchscreen issues.
On my device once I enable the "show the pointer location" -feature, I can clearly see that the device registers the touches right, but it behaves differently from the touches.
According to this I see, at least on my device, this more as a software than a hardware problem, and it looks that the problem is maybe even on a higher API level, which is IMO a good thing, because it _might_ be fixed with a firmware update. The question is, why Google hasn't done this yet, as the issue has been there around the world for a while, and there have already been a couple of updates (Q & R, or even more?) which haven't fixed the problems.
It would be interesting to hear reports of other devices. Test and report!
May82 said:
OK, so here's my problem. I recently returned my nexus 7 for a newer production date build because I had a horrible touch screen. I updated the new one and had missed touches/sticky keys but when I unlocked it to apply sfhub's fix it wiped everything and the problem is gone (maybe a bad upgrade install?) Every once in awhile it feels like it's still missing a touch. Like once every couple hours. I've noticed that the touch screen is very sensitive and if I move my finger a little bit while touching it registers as a swipe I guess. Is there a way to see if it's really not seeing the touch or registering as something different? There are no sticky keys whatsoever and multi-touch seems to work fine in a case or out. Does anyone else see this with theirs?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try playing some heavy multitouch games. I'm playing Terraria. Requires fine motion. You'll notice anything in that game.
Sent from my Nexus 7 using XDA Premium 4 mobile app
kotivalo said:
You can test/verify the touches by enabling the developer options on the Nexus.
To do this, go to settings, go down to "About tablet", and then down again to the build number. Tap the build number information ca. 5 times (5 to 10? after a few taps you will see an info sign about how many times you still have to tap), this enables the developer mode.
In the settings menu there should be now a new item, Developer options (just before the About tablet). In the developer options check the box named "Pointer location".
Now when you touch the screen, with one or more fingers, you can see a screen overlay with coordinates and axles showing where the device sees your touches.
I have the touchscreen problem with missing and sticky touches and pinch and twist problems, the whole menu. For example, using google maps or writing emails is a pain in the ass because of these touchscreen issues.
On my device once I enable the "show the pointer location" -feature, I can clearly see that the device registers the touches right, but it behaves differently from the touches.
According to this I see, at least on my device, this more as a software than a hardware problem, and it looks that the problem is maybe even on a higher API level, which is IMO a good thing, because it _might_ be fixed with a firmware update. The question is, why Google hasn't done this yet, as the issue has been there around the world for a while, and there have already been a couple of updates (Q & R, or even more?) which haven't fixed the problems.
It would be interesting to hear reports of other devices. Test and report!
Click to expand...
Click to collapse
Yeah i feel the same too. I think the problem is software/drivers related than hardware and i dunno if there is a "perfect" device out there at all. I feel many casual users are simply not experiencing it. What i find odd is that, it always feels better after a reboot and things start to deteriorate from there. Almost like memory is not being released properly and there's some stucked process being stacked etc etc. Personally i find that eliminating the use of Chrome entirely has worked better for me. Am using only Dolphin now and it's been going very well so far.
The latest touchmark results shows there is a high latency in the Nexus 7 2013 model. It also indicates that it could be due to frequency of CPU polling for touches with a combination of other things in GPU too. IMO i think the high DPI on the screen and the handling of the quadcore processor might require some tweaking to get it perfect. There seems to be too much latencies and perhaps the missed touches / stuck touches are due to a combination of problems in the code with regards to touch events handling. Oh well, regardless i think they need a taskforce behind it to resolve it.
http://appglimpse.com/blog/touchmarks-ii-touchscreen-latencies-in-flagship-tablets/
lomonic said:
http://appglimpse.com/blog/touchmarks-ii-touchscreen-latencies-in-flagship-tablets/
Click to expand...
Click to collapse
Interesting!
lomonic said:
Yeah i feel the same too. I think the problem is software/drivers related than hardware and i dunno if there is a "perfect" device out there at all. I feel many casual users are simply not experiencing it. What i find odd is that, it always feels better after a reboot and things start to deteriorate from there. Almost like memory is not being released properly and there's some stucked process being stacked etc etc. Personally i find that eliminating the use of Chrome entirely has worked better for me. Am using only Dolphin now and it's been going very well so far.
The latest touchmark results shows there is a high latency in the Nexus 7 2013 model. It also indicates that it could be due to frequency of CPU polling for touches with a combination of other things in GPU too. IMO i think the high DPI on the screen and the handling of the quadcore processor might require some tweaking to get it perfect. There seems to be too much latencies and perhaps the missed touches / stuck touches are due to a combination of problems in the code with regards to touch events handling. Oh well, regardless i think they need a taskforce behind it to resolve it.
Click to expand...
Click to collapse
Thanks lomonic, an interesting link.
I had the former/original Nexus 7 (until my oldest daughter accidentally dropped it in May), and it had no touchscreen issues, at least nothing as bad compared to my new Nexus 7 (2013 model). Yes, it lagged sometimes, as does also my Nexus 4 (mostly noticeable when you slide down the notification menu or open the open applications list), but it had no similar problems with the precision of the touchscreen of the new Nexus 7.
I just tried to reboot the device and also noticed the touchscreen performing a bit better. Though, the problem came back in no time, and after a couple of minutes using Google Maps was the same mess as before. Twisting/rotating the map with two fingers results to pinching/zooming and the map centers somewhere else you want it to. Also in Chrome zooming and scrolling doesn't work as expected, and selecting text is also problematic. Using the keyboard might get you a sticky backspace, which is somewhat annoying. I can only imagine how it would be to try to play touchscreen intensive games, which demand fast and precise touches.
On my Nexus 4 I've also noticed that Chrome seems to slow the whole device, and for this reason I've also been using Dolphin for a while now (but I've yet not deleted Chrome, I just don't use it). Maybe I should dump the whole app from my phone. Also using Clean Master to clean up the memory from apps/processes helps for a while, but only for a while.
Google (or Asus) could verify if there's a sw patch on the way. I'm not a gamer, I mostly use the tablet for surfing and reading, but also these task are not a pleasure with the touchscreen issue. If this problem still persist after a month or so, I really think about returning the device (I bought it just a week ago).
Chrome is super slow.
I don't know why but the stock Android Browser is super fast and awesome. I've been using Next Browser since it is based on Stock Android Browser but the past 2 recent updates have really screwed it up where it is beyond usable. Once it gets resolved, Next is really awesome. It is like Stock on Steroids.
However, regarding touchscreen issues, DON'T GO LOOKING FOR PROBLEMS. If you aren't having issues, then just relax and enjoy your tablet. If your tablet was plagued with a quirky touchscreen driver, then you would notice it. If you can't notice any issues, then you don't have any issues.
Sure there are tests you can run but why bother? It is a software problem and will be fixed eventually. This is not the first Nexus with quirky touchscreen drivers. In fact almost all of my Nexus devices had quirky touchscreen issues out of the box. All were corrected within a few updates. Even the Nexus One had a physical hardware problem with crossing axis that was alleviated using some Google Magic.
May,
I have the exact same issue--but my missed touches are once every 5 minutes--quite annoying when typing an email or typing a password. I haven't unlocked the tablet yet to apply sfhub's fixes--will let you know how it goes.
player911 said:
Chrome is super slow.
I don't know why but the stock Android Browser is super fast and awesome. I've been using Next Browser since it is based on Stock Android Browser but the past 2 recent updates have really screwed it up where it is beyond usable. Once it gets resolved, Next is really awesome. It is like Stock on Steroids.
However, regarding touchscreen issues, DON'T GO LOOKING FOR PROBLEMS. If you aren't having issues, then just relax and enjoy your tablet. If your tablet was plagued with a quirky touchscreen driver, then you would notice it. If you can't notice any issues, then you don't have any issues.
Sure there are tests you can run but why bother? It is a software problem and will be fixed eventually. This is not the first Nexus with quirky touchscreen drivers. In fact almost all of my Nexus devices had quirky touchscreen issues out of the box. All were corrected within a few updates. Even the Nexus One had a physical hardware problem with crossing axis that was alleviated using some Google Magic.
Click to expand...
Click to collapse
Stock android is fast but how do you get it with stock rom? chrome replaces it in 4.3 isnt it? OR are you on a custom?
I think the reality is that many are having problems but do not know about it. They may just dismiss it as not being accurate with their own touches. Also for some users, it could likely be their first touch devices and have no prior experiences to compare with. When i've gotten this device, it was working well and all, but it just feels like typing aint that smooth and slowly over time, the problems starts to be more frequent.
There was an incident i had when after a few days of usage, i tried using it with it lying on the bed and it was going crazy - which never happened before. I picked it up (attempt to earth it) and lay it back down again but the results are the same. So i did a reboot with the system on the bed, and all the problems went away. So i'm not sure it has to do with the earthing factor which many are citing.
I think it is a combination of GPU/CPU/memory and touch related event handling factors that causes the problems to occur more frequently after extensive usage. There should be no reason for hardware to perform perfectly after a reboot only to fail over time.
Oh well, only time will tell when these problems would eventually be addressed.
lomonic said:
Stock android is fast but how do you get it with stock rom? chrome replaces it in 4.3 isnt it? OR are you on a custom?
Click to expand...
Click to collapse
I guess you mean the stock android browser. It may not be available as an app but it's still there as a WebView component available to developers. I guess Dolphin and many other 3rd party browsers are based on the WebView component or on the source code of it.
The problem with the so called stock browser and WebView is that is uses some legacy HTML and JS engine that has not been updated since 2010 or so. That is another crappy developer "feature" from Google that for 3rd party developers there's no "web browser" component that is based on some up to date rendering engine like Chrome's.
In the Themes and Apps thread, there is a method to allow you to install the stock Browser on a stock rom without being rooted.
Also using Sfhub ts10 gave me a 90% fix but it would still spaz out occasionally and would miss touches or click weird stuff. ts20 really fixed me up right. I can play games now and type with no errors.
ts10 is a really good fix, but ts20 really hit it home.

Second Screen Lag

Hi everyone,
Has anyone noticed a second screen lag when swiping it around while the main screen is off? I only have the quick toggles and music player on my second screen when the main screen is off. But regardless of any direction you swipe it, there is a VERY considerable lag as it navigates to the next item. For those who previously had the LG v10 and are currently using the V20, I'm pretty sure you've noticed that the swipe on the V10 was very swift. I'm asking out of curiosity if anyone else has had this issue. It's possible that due to first batches of V20s available to the public, these units are suffering from it? Idk, I just want to hear your thoughts if possible. Thank you!
I'm experiencing the same thing.
Not mine, I have also the music player active and actually is pretty snappy.
no problems here. I'm not saying there's never been a lag, but generally not a lag on my Tmo version.
Sent from my LG-H918 using Tapatalk
When Pandora is playing the 2nd screen is noticeably laggy for sure. It doesn't impact how quick I can scroll around but it doesn't look great. Doesn't really bother me since the 2nd screen is too locked down to be that useful. I just leave it on Pandora controls or date/time
Yeah I'm seeing it too. Most of the time I need to double swipe it then it would jitter to the left when playing music. When not playing anything, it still has basic lag when screen is off.
Im noticing the same lag on mine as well when the main screen is off. Maybe something to do with battery saving.
Try this
Settings/Developer Options/ Tick on "Force GPU Rendering" this should make your beast smoother/snappier!
If root available try L Speed/Entropy/fstrim apps found on Play Store! LG V20 & LG G5 are both snappy beasts and most anticipated of 2016! They are well optimised with Snapdragon 820 and is better than Samsung.
I had this lag until I did a factory reset 3 days ago. I thought maybe it was the LG Home + App update from the lg app update so I didn't update until yesterday. The second screen lag is still gone. Maybe it was during initial setup that something borks. I don't know.
Sent from my LG-H918 using Tapatalk
beast330001 said:
I had this lag until I did a factory reset 3 days ago. I thought maybe it was the LG Home + App update from the lg app update so I didn't update until yesterday. The second screen lag is still gone. Maybe it was during initial setup that something borks. I don't know.
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
Hey beast,
So you recommend a factory reset? And you SURE it should be a bit faster or the lag would leave atleast?
saqc2010 said:
Hey beast,
So you recommend a factory reset? And you SURE it should be a bit faster or the lag would leave atleast?
Click to expand...
Click to collapse
I had to do a rest because of work and the little lag I had is gone.
Sent from my LG-H918 using Tapatalk
Pick_A_Name said:
I had to do a rest because of work and the little lag I had is gone.
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
Thanks. So how soon did you notice the lag and how quickly did you do the reset. Other than the screen lag being gone, did you notice any other changes or flaws?
saqc2010 said:
Thanks. So how soon did you notice the lag and how quickly did you do the reset. Other than the screen lag being gone, did you notice any other changes or flaws?
Click to expand...
Click to collapse
Honestly I didn't notice the lag until this thread pointed it out. Probably because I've had Samsung devices for so long that lag is just part of life. Since factory resetting it, I've noticed it just runs better in general and not just the second screen lag.
Sent from my LG-H918 using Tapatalk
saqc2010 said:
Hey beast,
So you recommend a factory reset? And you SURE it should be a bit faster or the lag would leave atleast?
Click to expand...
Click to collapse
The second screen lag hasn't returned for me after the factory reset. It swipes left or right very quickly.
I do get a random lag from several hours/days uptime on the regular screen though. A restart fixes that lag for me.
Sent from my LG-H918 using Tapatalk
My screen was lagging so I reset all the defaults that go with the second screen and it now runs smoothly so long as my battery percentage is above 25%.
Almost 3 weeks and I've experienced no lag at all on second screen, always fast and fluid however it's been set up.
@Olivia1234
I'm curious why you think battery % would make any difference. Have you actually confirmed it does?
And welcome to XDA.
Same here. I am having lag on stock and now running mega rom on my 918. I have to swipe a couple of times and then it will skip the toggles I want ? maybe it's meant to be laggy so toggles aren't pressed by accident? Or so it's not swiping back and forth in your pocket??...either way it's very annoying
Nah mate, you not read my post above yours?
It should behave the same as main screen, be dumb to purposely make it behave like yours is.
Only time I have lag so to speak is when the phone has been sleeping for awhile in my pocket. When I take it out and wait for the 2nd screen to turn on and I try swiping sometimes it'll take a 2nd swipe or so. Almost seems like doze or deep sleep and it's not kicking it up fast enough to respond in time. So far has happened to stock, WETA and MegaRom.
Very annoying how long it takes for the phone to wake up when it's been in pocket. It won't even register the power button press to turn it on or the double tap to wake until the 2nd screen has turned back on
KUSOsan said:
Only time I have lag so to speak is when the phone has been sleeping for awhile in my pocket. When I take it out and wait for the 2nd screen to turn on and I try swiping sometimes it'll take a 2nd swipe or so. Almost seems like doze or deep sleep and it's not kicking it up fast enough to respond in time. So far has happened to stock, WETA and MegaRom.
Very annoying how long it takes for the phone to wake up when it's been in pocket. It won't even register the power button press to turn it on or the double tap to wake until the 2nd screen has turned back on
Click to expand...
Click to collapse
I've experienced that exact same thing. Sometimes I try to unlock it to fast and it just locks again no big deal for me though. I just ran across an issue running MegaRom.
Not sure if it has anything to do with the room though anyway the quick tools on the second screen are gone. If you scroll from the signature to the quick tools menu it's just black if you tap where the icons should be they work it's just like they are invisible or black I'm thinking it might have something to do with Nova launcher but I'm not sure I've played with the settings in Nova for about a day and it hasn't changed.

Randomly low performance?

Hey I just got my Z4. Upgraded from a Z2 Play. I bought direct from Motorola off their website. I'm having really strange 2D performance issues, and was wondering if anyone else is having similar issues because they seem outright stupid for a phone as beefy as this one is to be doing this.
OK, so, this is going to sound super vague because I did try to nail it down with a ctrace, but wasn't able to come up with anything conclusive.
Sometimes, when drawing 2D only, my phone will drop to 30fps or lower. This happens in both in the launcher/normal apps and games (Fire Emblem Heroes)
However, when the phone is drawing in 3D (Dragalia Lost) the phone never drops below 60fps, ever, for any reason.
I have tried the developer option to force 2D Drawing on the GPU. This does not change the behavior at all.
This happens regardless of what MotoMod I have attached (None, Car Dock, Projector, 360 Camera)
This seems really weird to me. The phone isn't getting hot. It happens both plugged in and unplugged. Fresh reboots and not. What's interesting about this is it's exactly the opposite of my Z2 Play, which Dragalia F***ing hated (It would run fine for anywhere from 5 to 30 minutes, and then it would crash) but FEH would run fine on, and never ever have issues, ever, even if the phone hadn't been rebooted in like, 3 months. And the Z2 Play is just generally a weaker, crappier device in every way (Except Ram, I had the 64gb/4gb model of the Z2 Play) than the Z4, I kind of "expect" the Z4 to just do everything the Z2 did but better.
I'm not a particularly heavy user (I upgraded from my Z2 Play because the battery was expanding, not because it was insufficient) and both of the games mentioned are the only things I do on my phone that could be considered to "Push" the phone in any way (Push in quotes because Dragalia and FEH are both REALLY light games.)
Has anyone else noticed any strangeness like this?
I have the same issue, and yes, it's really hard to describe and difficult to determine what causes it.
What it actually looks like to me is that the digitizer randomly goes into a powersaving mode and samples input at a lower frequency. When scrolling through any app, if you hold your finger down, it'll make it look like it's running at 30fps or less. But if you fling a page that can scroll, for the most part the scrolling animation will be full 60fps.
I know for certain that if you reboot the phone, you're more likely to trigger it soon after boot. But, if you suffer through the agonizing experience, the phone will eventually fix itself for the next week or so before it happens again.
Here's the weird part, not everyone is affected by the weird performance. My theory is most people can't detect it or don't care, or there's a particular app that is prompting the digitizer to behave badly. No idea what it is though.
damentz said:
I have the same issue, and yes, it's really hard to describe and difficult to determine what causes it.
What it actually looks like to me is that the digitizer randomly goes into a powersaving mode and samples input at a lower frequency. When scrolling through any app, if you hold your finger down, it'll make it look like it's running at 30fps or less. But if you fling a page that can scroll, for the most part the scrolling animation will be full 60fps.
I know for certain that if you reboot the phone, you're more likely to trigger it soon after boot. But, if you suffer through the agonizing experience, the phone will eventually fix itself for the next week or so before it happens again.
Here's the weird part, not everyone is affected by the weird performance. My theory is most people can't detect it or don't care, or there's a particular app that is prompting the digitizer to behave badly. No idea what it is though.
Click to expand...
Click to collapse
It's definitely not the digitizer though! I have some data! Fire Emblem Heroes has an autobattle mode, This is as likely to happen during an autobattle when I am providing no input (Phone sitting on desk/just watching while holding) as it is when I'm scrolling through my list of apps.
Same problem here, pretty sluggish experience compared to my girlfriend's G7 Plus.
I've noticed that since the latest update, this issue has gone away for me. Anyone else confirm?
I don't think it was the update, but certain apps seem to exaggerate performance issues. I fixed mine by marking Pokemon Go (the only 3d game I play), as "Restricted" under battery usage settings.
I've been testing this configuration for about 2 days now and it looks like that solved it.
Just to set the record straight, the Android 10 update fixed the random performance problems that have plagued the device so far. There is some hitching right after a reboot, but if you let the phone settle, it's fine until the next reboot.

Resources