Database Users

Vibrant Lag on Power button

Hello,
So I am aware of the Lag with the vibrant being a known issue. However, I have an interesting quandary. I own two of these, one for my wife and one for myself. I already had to replace mine for poor radio performance, now the replacement has a whole new set of problems. The display is saturated in contrast by comparison to my wifes original. and the biggest problem is a lag when the device is locked. As we all know, you hit the power button and the swipe-to-unlock screen populates. On my wifes this transition is instantaneous. For mine, I hit the power button and only occasionally will it come on instantly. Most cases, it takes a second or longer before the unlock screen ever populates. So what's going on here? Do these things just suffer high fail ratio?

Just high complainers I have 0 issues....

This would be easily dismissed as a guised complaint if I didn't have two devices of the same model behaving differently. While one works great, I've gone through two. One had a radio that would drop inexplicably and now one that is extremely lagged and has a noticeable contrast saturation in the display.

Ha. There is a VERY slight delay when waking the device. Boo-hoo.

A legitimate problem and this is the reaction?
If it takes a full second to unlock one phone and near instant on everyone else's, maybe there really is a problem with it?
I don't have this problem on mine, but I do hope you're able to find a solution to your problem.

I've noticed this happening to mine as well and it's kind of bothered me since the beginning. For being a 1ghz "super-phone" I'd expect it to be a little more responsive when performing the simple task of unlocking it. I've also noticed that once the screen starts to light up, it does so a little choppy. It doesn't smoothly transition from off to on. When I press the the power button there's about a 1 sec delay, then the screen goes from off to half lit to fully lit.
Does this happen to anybody else?

I had the same problem, until I did the "Stalling fix." Hasn't happened since.

I've seen this once or five times on my Vibrant, too. But my G1 would wake slowly on occasion too.
-bZj
_____
-sent from my Samsung Vibrant via XDAapp

I've noticed if some kind of sync was occurring as I powered on my g1 or even the vibrant (before the stalling fix), it caused a slowdown. Network traffic was just eating up some resources and it was made a more pronounced with the way Samsung sliced the memory on this phone and the data it was syncing was on the slower memory (stalling). Usually, I'd see the icon lit up in the bar at the top. I'd go back and off/on it a few times and it would be fine. Of course, the sync would have been over with by then. But just as Bahnburner said, it pretty much went away after moving data to faster bit switchers.

down8 said:
I've seen this once or five times on my Vibrant, too. But my G1 would wake slowly on occasion too.
-bZj
_____
-sent from my Samsung Vibrant via XDAapp
Click to expand...
Click to collapse
That's the G1, though. My mytouch was pretty responsive, even after I loaded cyanogenmod 5 and 6. I never had this problem with that phone.
Another example of my screen unlocking lag issues:
Just now, as I was typing this, my phone completely froze when I tried to wake it up. I pressed the power button and the screen came on, but the phone became completely unresponsive. I waited for about 20 seconds until I lost patience and removed the battery to reboot it. This was the first time it happened since I got it on Thursday, but it still has me a little worried.
Even after a fresh reboot I get the 1 second screen wake up lag, and then a laggy transition from off to lit screen.
This is really the only issue I'm having with the phone. I don't experience lag anywhere else. I'm wondering if this is normal with other users or if I should get it swapped out.

its such a small delay, i didnt think it was a big deal :/

I have no lag waking it up whatsoever. I did have freezing when killing certain System apps. I stopped doing that and everything has been fine save for the occasional pause.

Try down loading no lock app. It will unlock your phone with one push of the power button taking away the need to swipe the phone.
Feeling Vibrant on xda-app

tq745 said:
Try down loading no lock app. It will unlock your phone with one push of the power button taking away the need to swipe the phone.
Feeling Vibrant on xda-app
Click to expand...
Click to collapse
with this app, you can also unlock the phone with the volume buttons..

Non-rooted Vibrant random restart?

It seems to happen after the phone has been on for an extended amount of time. I don't have lag, and I'm not using the gps when it happens. In fact, it usually happens when I sleep. Has anyone else experienced this? My phone is not modified. I'm even running plain touch whiz. I'm considering returning if I can't resolve with a hard reset. No third party apps are running when this occurs. I routinely close processes before I stop using the phone. I love this phone, I'm just worried I have a bad unit.

i'm having a similar issue, but with a rooted vibrant. the problem has spanned across two different handsets. the first one i rooted almost out of the box. but after a few days it started locking up after sitting for a while and i would have to pull the battery to get it to come back on. so i returned it, got a new one and held off rooting it to see if this one would do the same thing. the non rooted one had no problems at all, so i bit the bullet and rooted this one too, and sure enough later that same day it started doing the same freezes when trying to unlock it.
as soon as i rooted the second phone i downloaded rom manager and made a nandroid backup. after the backup i proceeded to remove some of the bloat, like dual clock, the startup/shutdown sounds, and some of the other crap that the vibrant comes with. i also installed and started up setcpu. it seemed that after i did all of this is when the freezes started up again. so i did a restore to before i removed all that stuff and now the phone is fine again. what is it about my process that is making this phone lock up like this?
EDIT: nevermind...i found some other people with the same problem in a setcpu thread...seems setting the sleep profile too low will cause the phone to not wake up after sitting too long

Uh, I'm not getting any freezing, but I know there is an issue with SetCPU. A certain setting will causes problems on the Vibrant. My issue is just unexpected reboots after the phone has been on for approximately 170 hours.

I had many random restarts and general craziness from my non rooted stock vibrant. A factory restore fixed all problems.
Sent from my SGH-T959 using XDA App

Yeah, if it happens again I'm going to try a factory reset.
Sent from my SGH-T959 using XDA App

Issues since updating my Bravo

I would like to start this out by saying that I have had my Bravo since January 16, and have loved every minute of it. This has been my first Android (Came over from my iPhone 3G). I was extremely excited to finally get the upgrade to 2.2, even though I decided to wait to officially download it OTA.
Since I got my phone, I had no more than three to five apps force close on my using the stock launcher. I rarely noticed much of any lag while working with my phone, and I never once had any issues with the phone rebooting itself on me.
Since I updated my phone on Saturday I've been plagued with all of these issues. Immediately after updating, I noticed my phone was running very hot, and my battery drained to 50% within an hour or two without me even running anything stressful on it. I restarted it twice and since then I haven't noticed any significant issues with my battery, or the phone seeming to run it's processor excessively.
But, I have constant lag, making tasks that were extremely quick and easy before the weekend be significantly more difficult and frustrating. Today I've even noticed that the lag is so bad that I am not even able to use Swype because the phone takes so long to register any touch's it doesn't register anything other than the first and last letter I swyped across. In addition, my phone has rebooted itself 3 times within the last three days I've been using it, an issue that has not happened once in the three months before this weekend.
I will regularly be trying to do things on my phone and it will lag, causing the phone to freeze for 20-30 seconds at a time, and then trying to perform every touch it received in those 20-30 seconds in a scant second after it recovers.
I have noticed some issues not regarding lag, but sometimes it has been difficult for my phone to initiate calls. I have tried to call my wife, and it took 5 times before the call would finally go through, it was immediately ending the call right after I pressed the call button.
I love my phone and the capabilities of the Android system. Until now I haven't had any problems at all with it. Can you help me try to figure out what's happening, and if there are any ways to fix my phone? I haven't gotten around to rooting my phone since I've gotten it, but have been planning on it.

roadkizzle said:
I would like to start this out by saying that I have had my Bravo since January 16, and have loved every minute of it. This has been my first Android (Came over from my iPhone 3G). I was extremely excited to finally get the upgrade to 2.2, even though I decided to wait to officially download it OTA.
Since I got my phone, I had no more than three to five apps force close on my using the stock launcher. I rarely noticed much of any lag while working with my phone, and I never once had any issues with the phone rebooting itself on me.
Since I updated my phone on Saturday I've been plagued with all of these issues. Immediately after updating, I noticed my phone was running very hot, and my battery drained to 50% within an hour or two without me even running anything stressful on it. I restarted it twice and since then I haven't noticed any significant issues with my battery, or the phone seeming to run it's processor excessively.
But, I have constant lag, making tasks that were extremely quick and easy before the weekend be significantly more difficult and frustrating. Today I've even noticed that the lag is so bad that I am not even able to use Swype because the phone takes so long to register any touch's it doesn't register anything other than the first and last letter I swyped across. In addition, my phone has rebooted itself 3 times within the last three days I've been using it, an issue that has not happened once in the three months before this weekend.
I will regularly be trying to do things on my phone and it will lag, causing the phone to freeze for 20-30 seconds at a time, and then trying to perform every touch it received in those 20-30 seconds in a scant second after it recovers.
I have noticed some issues not regarding lag, but sometimes it has been difficult for my phone to initiate calls. I have tried to call my wife, and it took 5 times before the call would finally go through, it was immediately ending the call right after I pressed the call button.
I love my phone and the capabilities of the Android system. Until now I haven't had any problems at all with it. Can you help me try to figure out what's happening, and if there are any ways to fix my phone? I haven't gotten around to rooting my phone since I've gotten it, but have been planning on it.
Click to expand...
Click to collapse
Something probably is messed up in the upgrade process.
Simple solution, flash the 2.2 sbf and you should be good.

roadkizzle, Something doesn't sound right at all with your update. I would try to remove the battery for a minute and reboot. If you still have issues I would try a factory data reset. If that doesn't cure your ills then flashing the 2.2sbf as bandroidx suggested may be in order.

Alright, I flashed the SBF file to the phone through RSDLite, and from what I can see it went through correctly. My only question now is do you think I'll need to try to re-install the full update? Or is that similar to what I did?

roadkizzle said:
Alright, I flashed the SBF file to the phone through RSDLite, and from what I can see it went through correctly. My only question now is do you think I'll need to try to re-install the full update? Or is that similar to what I did?
Click to expand...
Click to collapse
flashing the sbf already updated your phone to 2.2. You don't need to do anything else

I hope reflashing did the trick for you. That experience sounds nasty...
Sent from my MB520 using XDA App

Well, after a couple of hours of playing with my phone it's seeming better. I have been playing a few games of Worms, and my normal surfing the internet and so far I haven't noticed any real lag. The test will be my day through tomorrow.
I was just really confused because I was following the instructions from the Flashing SPRecovery SBF to a Motorola Droid youtube video, and his SBF file really seemed to only change the recovery screen. It looked like he still had to go through the actual update.zip process to make the actual updates to his phone.

Alright it's official, flashing the sbf did not fix the lag issues. My phone hasn't had a critical malfunction and reboot itself yet today, but the lag is unbearable.

roadkizzle, It sounds like you are still having issues. If you look at the system version in "about phone" in settings menu does it say version 37.4.0.MB520??

Yes, it says Version.37.4.0.MB520.ATT.en.US

roadkizzle said:
Alright it's official, flashing the sbf did not fix the lag issues. My phone hasn't had a critical malfunction and reboot itself yet today, but the lag is unbearable.
Click to expand...
Click to collapse
what apps do you have installed?

look in task master and get rid of any auto-ends and reboot and see if that makes a difference

Well, immediately after removing the AT&T apps from the auto-end list and rebooting, I thought I noticed some lag initially, but I've let it run for a few days now doing everything I was before and I've not been having any of those issues recently.
I'm not sure what it was. I wasn't very aggressive adding apps to my auto-end list, really just Maps and the AT&T apps. I added maps after a while because when I would use it once it would stay open and I'd notice later on that it would have been a major consumer of my battery, and I couldn't figure out how to close it fully.

Glad to hear things are going better. I had some issues totally unrelated to the apps I had in auto-end but pulling all of them off of auto-end got rid of the issues. Froyo is supposed to minimise the need for having to add apps to auto-end in task manager. Regards

(SIA for the long post)
roadkizzle - my situation sounds very similar to yours and I wanted see if you are also seeing a couple of other symptoms I've seen beyond what you have indicated. This has been an issue from early on for me. At first it seemed to be associated to when the battery was low, but it is now ever increasingly interrupting my use of the phone. I was hoping 2.2 might resolve some of this, but it hasn't.
Background: Purchased/activated phone early Jan 2011; recently upgraded to the 2.2 sys and used the official channels; all apps I've added are lightweight stuff (ex: notepad-type stuff, weather widget) and I have pushed most unused stuff to the auto-end list.
Similar symptoms: I see the same power drain and high CPU usage when using maps/navigator (really evident on a recent trip). Still monitoring if some of that can be attributed to use of the GPS.
I'm getting a similar lag though I wish it was only for the short period you are seeing. I've only rarely been able to just put the phone down and have it responsive when I get back to it. Maps/Navigator were especially susceptible to this problem, and it seemed consistent with the 90%+ CPU usage often seen when they are running.
I don't use swipe, but the keypad is most often what is being used when the lag kicks in... the entire phone just goes completely unresponsive, including any and all other input such as the hardware home/back keys, etc.
In addition: Better than half the time that the qwerty touchpad becomes unresponsive, I see sporadically entered random keystrokes to my messages... everything from initiating the voice input to entering several dozen spaces or just simple random characters. This happens at a random, often changing rate and I see the keys lighting up and the haptic responses happen as if I were touching the keys, but they are not from any delay in the input. Once ruling out an exorcism, this has started me thinking I might have a hardware issue with the touchpad. The phone has not been dropped or roughed up in any way, so if it is HDWR, it's a manuf issue.
Luckily.... in 99% of the cases where this happens, using the HDWR power button to cycle the screen through a sleep and back resolves the issue. Not a big deal unless you have to do it 3 times to send one text/mail. This has me constantly thinking about items on the auto-end list but I have not unearthed anything to support that.
The other 1% of the time I have had to reboot the phone, but in those cases I can't rule out 'user issues' due to just pure frustration. Task Manager has become my most freq used app, but often I see everything at 0% CPU and/or not running.
I'm wondering if any of these additional symptoms sound familiar...
thx.

humanque said:
(SIA for the long post)
roadkizzle - my situation sounds very similar to yours and I wanted see if you are also seeing a couple of other symptoms I've seen beyond what you have indicated. This has been an issue from early on for me. At first it seemed to be associated to when the battery was low, but it is now ever increasingly interrupting my use of the phone. I was hoping 2.2 might resolve some of this, but it hasn't.
Background: Purchased/activated phone early Jan 2011; recently upgraded to the 2.2 sys and used the official channels; all apps I've added are lightweight stuff (ex: notepad-type stuff, weather widget) and I have pushed most unused stuff to the auto-end list.
Similar symptoms: I see the same power drain and high CPU usage when using maps/navigator (really evident on a recent trip). Still monitoring if some of that can be attributed to use of the GPS.
I'm getting a similar lag though I wish it was only for the short period you are seeing. I've only rarely been able to just put the phone down and have it responsive when I get back to it. Maps/Navigator were especially susceptible to this problem, and it seemed consistent with the 90%+ CPU usage often seen when they are running.
I don't use swipe, but the keypad is most often what is being used when the lag kicks in... the entire phone just goes completely unresponsive, including any and all other input such as the hardware home/back keys, etc.
In addition: Better than half the time that the qwerty touchpad becomes unresponsive, I see sporadically entered random keystrokes to my messages... everything from initiating the voice input to entering several dozen spaces or just simple random characters. This happens at a random, often changing rate and I see the keys lighting up and the haptic responses happen as if I were touching the keys, but they are not from any delay in the input. Once ruling out an exorcism, this has started me thinking I might have a hardware issue with the touchpad. The phone has not been dropped or roughed up in any way, so if it is HDWR, it's a manuf issue.
Luckily.... in 99% of the cases where this happens, using the HDWR power button to cycle the screen through a sleep and back resolves the issue. Not a big deal unless you have to do it 3 times to send one text/mail. This has me constantly thinking about items on the auto-end list but I have not unearthed anything to support that.
The other 1% of the time I have had to reboot the phone, but in those cases I can't rule out 'user issues' due to just pure frustration. Task Manager has become my most freq used app, but often I see everything at 0% CPU and/or not running.
I'm wondering if any of these additional symptoms sound familiar...
thx.
Click to expand...
Click to collapse
Try taking things off of the auto-end list. You shouldn't need the task killer because android manages apps on its own (it's supposed to manage apps better in froyo than in 2.1)

I've also had lag, especially when opening maps (the first time I open maps it often force closes).
Can anyone get the "lock pattern" screen without the slide to unlock? It seems like a common "Motorola 2.2" issue, but I can't figure out if it gets resolved through an update or not

kyngnothing said:
I've also had lag, especially when opening maps (the first time I open maps it often force closes).
Can anyone get the "lock pattern" screen without the slide to unlock? It seems like a common "Motorola 2.2" issue, but I can't figure out if it gets resolved through an update or not
Click to expand...
Click to collapse
it can be fixed through the settings.db in the com.android.providers.settings, but i dont remember what to edit inside.
or you can download No Lock from the Market
https://market.android.com/details?id=org.jraf.android.nolock

jorgonv said:
it can be fixed through the settings.db in the com.android.providers.settings, but i dont remember what to edit inside.
or you can download No Lock from the Market
Click to expand...
Click to collapse
NoLlock just seems to turn the lock screen on and off altogether?
I can get the screen lock on and off, I just can't get the pattern lock without the side-to-side swipe lock at the same time
This is messing with
PS . If you can't get your screen to stop locking all the time with froyo 2.2.1dissable it in the same location ID # 61 screen_lock set to 0. ),
Click to expand...
Click to collapse
and the settings menus.
There are several other seemingly lock-related database settings, but I'm worried about locking myself out

kyngnothing said:
NoLlock just seems to turn the lock screen on and off altogether?
I can get the screen lock on and off, I just can't get the pattern lock without the side-to-side swipe lock at the same time
This is messing with
and the settings menus.
There are several other seemingly lock-related database settings, but I'm worried about locking myself out
Click to expand...
Click to collapse
You can always sbf if you get locked out. your data will also be kept

CQATest app on Marshmallow Causes System Issues?

Thought I would share this here - though I believe this is effecting other Moto models as well.
The Moto app "CQATest" seems to be the culprit with major instability issues I've had since the Android Marshmallow update. Before the update, my phone was so smooth and fast. Then the update came, and I blamed it on Marshmallow. Screen response to anything was very slow. Sometimes completely unresponsive. If i tried to touch a notification in my notification bar, it might be 5-10 seconds later before anything would happen, and the app would open. Sometimes it wouldn't ever open at all. Or when Facebook did open, it might take another 10-15 seconds before it went to the item it had notified me about. The camera in particular was slow to respond - with visible lag whenever trying to take a video - or would just crash. The phone itself got into a fairly normal habit of rebooting itself several times a day. And on startup, sometimes it would take 3-5 minutes before it would finally get to the home screen. Simply unacceptable.
So yesterday I started Googling for answers, and ran across a thread on Android Forums talking about issues people were having with CQATest. I immediately went and found the app in the settings>applications menu, under "All Apps" - force stopped and disabled it, then rebooted.
Guess what? The phone boots normally again! And the general responsiveness and functionality are back to what it was prior to the Marshmallow update. I couldn't be more pleased right now - because I was getting very frustrated with what is a relatively new phone.
I'd be interested if others have experienced something similar? Or are having similar lag issues and try this solution to see if it works for you.
Mods - if this CAN be confirmed, it really should be shared with ALL Moto users who've been upgraded to Marshmallow and have similar issues. The Android Forums thread user was originated by someone on the Moto X for instance.
Thanks for your time and feedback.

Do you have any misbehavior since you've disabled CQA Test? Like something doesn't work... Are you getting better battery life? I think you should.
I have Moto X Force, didn't touch app and system is smooth, stable with great battery life. I suppose you have Turbo 2.

No apparent issues with anything else since disabling it that I can see. And yes, I'm on a DT2.

Zeljko1234 said:
Do you have any misbehavior since you've disabled CQA Test? Like something doesn't work... Are you getting better battery life? I think you should.
I have Moto X Force, didn't touch app and system is smooth, stable with great battery life. I suppose you have Turbo 2.
Click to expand...
Click to collapse
I have had CQA Test disabled before and after Marshmallow and notice no misbehavior. I also have been using advanced calling since i got the phone on launch day and have never had a problem with the call quality as others have.

CQATest not causing problems on my Droid Turbo(1)
I just got a refurb Droid Turbo on Marshmallow, and I've had others. I was experiencing some of those same issues that you described.... extremely slow boot and shutdown, and lag on launching apps or other screen clicks.
I just disabled the following and was amazed at the speedy boot time and responsiveness:
CQATest
Amazon (old app.... new one is Amazon Shopping)
Connect
Message+ (verizon sms)
Mobile Hotspot
After that first boot, I re-enabled CQATest and have rebooted several times since. It still seems fast and responsive. I've got a boot time of 35 seconds to the home screen, shutdown time of about 10 seconds.
Just to check, I disabled CQATest again, shutdown and started. The times are the same as above. I was hoping to explore the CQA menu, but haven't been able to so far. I've got USB debugging enabled, but not plugged into a computer. I'll look for answers in other threads.

GeckoDad said:
I just got a refurb Droid Turbo on Marshmallow, and I've had others. I was experiencing some of those same issues that you described.... extremely slow boot and shutdown, and lag on launching apps or other screen clicks.
I just disabled the following and was amazed at the speedy boot time and responsiveness:
CQATest
Amazon (old app.... new one is Amazon Shopping)
Connect
Message+ (verizon sms)
Mobile Hotspot
After that first boot, I re-enabled CQATest and have rebooted several times since. It still seems fast and responsive. I've got a boot time of 35 seconds to the home screen, shutdown time of about 10 seconds.
Just to check, I disabled CQATest again, shutdown and started. The times are the same as above. I was hoping to explore the CQA menu, but haven't been able to so far. I've got USB debugging enabled, but not plugged into a computer. I'll look for answers in other threads.
Click to expand...
Click to collapse
My DT2 was suffering from slow-downs for a couple weeks, then suddenly had the random shutdown and power-only-on-charge scenario yesterday. I was getting ready to do a factory reset.
On one of the reboots, I had a notification about CQA test. When I acknowledged it, I got notifications that "CQATest wants to access this," and "CQATest wants to access that." I denied them all and started hunting up this app I'd never heard of. That's when I came across this thread. I disabled CQATest, but still had the problem. I then remembered that the "old" Amazon app had just updated. I force-closed it, disabled it, and now the phone is back to normal. I see no need for CQATest, so I'm leaving that disabled, but I firmly believe that the Amazon app was culprit.
EDIT: I may have typed to soon. The phone shut off randomly twice today, requiring connection to a power cord to bring it back to life. It does, however, remain powered up upon disconnection (for now?).:-/ I did not clear the cache after deactivating those apps, though, so we'll see if that does the trick.
..

Hi there.
Backstory: My DT2 is almost 3 years old. I already had to send it back to Motorola once for a camera issue, but generally I didn't have any major performance issues for the first year and a half or so. Then it started to decline. Namely OS was taking longer to respond, battery life declining. Then when it was about 2 years old it began the random shutdowns. For the last several months I haven't really had the random shutdowns, however, my battery has been pitifully horrible at holding a charge, and it will usually shut down before the battery indicator hits 0%. First it was around 15%, gradually getting worse. Now it often shuts down between 30-40%, especially if I haven't been on battery saver since disconnecting from the charger.
Now today, I ran down my battery within a few hours to about 30% and it shut off, which was not abnormal. However, upon connecting to charger and attempting restart, the battery indicator jumped from 30 up to 40, then down to 4. Got a weird screen before startup that looked like a system error screen and was afraid it was going into factory reset without my prompting it. Pressed the power key once briefly and the phone went into normal startup, but when it turned on, CommServer was stuck in notifications bar and battery indicator was stuck at 3%, similar story to the others in this thread and others.
I disabled the apps suggested by GeckoDad, and so far the phone can operate, but I've had it plugged in for maybe 30 minutes and it's still hanging out at 3%. Was planning to get a new phone soon, but had hoped to wait another month or two... Probably going to head over to Verizon this afternoon to see if they have any suggestions to keep my DT2 alive until I'm able to replace it.

Weird screen jitter/touch ..phone going crazy

Occasionally my phone will just go crazy, screen will get all jittery,touching on a menu doesn't work ,it mainly happens on noughat stock and custom ROMs.,random apps popping up.any experience anything like that?a simple reboot fixes the problem.

russ722 said:
Occasionally my phone will just go crazy, screen will get all jittery,touching on a menu doesn't work ,it mainly happens on noughat stock and custom ROMs.,random apps popping up.any experience anything like that?a simple reboot fixes the problem.
Click to expand...
Click to collapse
It's an inherent issue with some displays present on the Moto G4. It most often happens when you charge your phone. Too much current builds into the frame of the display and you get weird ghost and jitter touches.
No way around it unless you send it in, and even then it may be only a temporary fix.

I also face this issue. Unable to find solid solution for this. Finally i decied to go for custom rom like RR and Invicta. This still comes occasionally(when Heats too much during phone charging)

russ722 said:
Occasionally my phone will just go crazy, screen will get all jittery,touching on a menu doesn't work ,it mainly happens on noughat stock and custom ROMs.,random apps popping up.any experience anything like that?a simple reboot fixes the problem.
Click to expand...
Click to collapse
On my phone this happens while not charging. Seems to happen about one out of every 3 times the phone is unlocked using the fingerprint sensor. Locking the screen and unlocking via a pin seems to be a reliable way of getting past the issue. Though occasionally it happens on the pin entry screen before it the pin has been entered. Needless to say, it IS annoying.

Same problem which is fixed.
I had this problem with the factory firmware too, intermittent bouts of the phone going crazy with phantom touches on my Moto G4. I sent it to Motorola/Lenovo after the supplier gave me their phone number and they did find the problem and fix it. Now I can play graphic intensive games even during fast charge and the phone is awesome for once. : )
Please note they will fix it for free if in warranty and bootloader not yet modified.

Pressing power button to turn off the display and then pressing power button again to turn the display back on will provide temporary relief from jittery screen. I noticed that the jittery screen has twice subsided over time but came back twice immediately after OS upgrade so blaming the problem on charging, or hardware doesn't seem accurate.
Updated 5/20/2018
As a last ditch effort prior to buying a replacement phone I deleted all apps I installed, reset phone and reinstalled fresh copies of most if the apps I needed.
I don't recall every thing I did but my focus was to delete everything I could and then reset phone back to factory state. After reinstalling, my jittery problem went away and has not returned. Your millage may very, so no promises. Phil

. I have touch screen issue(ghost touch) but this time not screen burn issue.. Now there is in winter.. I have checked battery temperature with ex kernel manager. When i go outside in fog or cool weather and when battery temprature goes to less than 20 degree Celsius phone gonna mad..back key home button automatically pressed..Is there any solution? Without going service center And fix battery battery temperature to 25 degree.?

phone going crazy
Hi,
I am having the same exact problem. I have observed that Google Assistant is intruding because each time this happens, Google Assistant is trying to run. Reboot is a temporary fix but the problem persists. I have removed most of the third party apps just to see if anything changes but it did not work.
This is not something that was happening from the start. I have the phone for about 2 months put the problem only started a couple weeks ago. I would love to hear if there is a solution and what. Thanks

Sadly, but compared to the issues visible indoors, in outdoors this Lenovo gift turns complete crap:
youtu.be/dTcHclVEfCg
"Lenovo Moto Z2 Force touchscreen gets completely unusable when getting outdoors! The video is made at about 0 degrees Celsius. So it takes about 30 sec from getting MotoZ2 Frc to sleep with pwr btn (and wakeing up back) to see the touchscreen goes crazy. At -10C, it takes ~5 sec. At +15-20C, after several min it becomes unresponsive and have to use pwr button to recover.
Lenovo, what you have done to Motorola ?!!"
Can it be fixed somehow with changing the upper protective part? I have seen comments that the touchscreen can stop working completely, if peel off the cover part..