Related
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.
I've been having problems with device Encryption and the external storage not mounting, but I recently noticed that after enabling Secure Startup on my Galaxy S7 Edge running 6.0.1 for Verizon and left at this screen for longer than a minute without touching it, a clicking sound as if you were pressing buttons or entering the pattern can be heard. It's continuous and clicks every other second. I Reset All Settings, Reset Network Settings and even applied updates as well as restarted the phone after turning Secure Startup off and back on, but it's still happening. Not exactly sure if this is expected, but I couldn't imagine it would be, especiall due to the fact it's really audible. Any advice or suggestions would be great! I'm really at my wits end with this phone and I'm ready to throw it away. The encryption problem I had originally (found here: SD Card No Longer Available (Encrypted) After Firmware Update) is still an issue even after applying the latest updates and I can't afford to lose all the data on my SD card again.
First off, I'm running stock-rooted, 7.1.1 - No Xposed installed. It's been running fine since the update came out (a few weeks).
Out of nowhere, my Axon 7 rebooted yesterday evening? It was sitting on a table, hadn't been dropped or anything.. After the reboot, it froze up and I had to reboot it.
Throughout the night, it rebooted a few times and I had to force re-start it even more. Then it wouldn't recognize my SD card on a few of the reboots (could my SD card be going bad)?
I'm having issues with my Playstore, other than "Waiting for Network" (yes, I'm having that too though). Downloads won't update, saying "try again later".
I tried a factory reset and didn't load any of my apps, same issues.
I'm getting ready to completely reformat my phone and start over.....Is anyone else having these issues, just out of no-where?
Mine spontaneously rebooted yesterday too. It then blasted the startup music even though that's turned off. It then had no data, as usual, and needed airplane mode cycled. My experience is that cell towers nearby matter. My phone works moderately well in some places but the radios crash every 30 seconds in others. Maybe you now have carrier aggregation in your area. T-Mobile 2+4 CA crashes mine constantly.
I wish I could believe that this would be fixed soon but I dropped out of the beta program because it seemed like ZTE just wanted a count of dead phones for each new build. I'd like to congratulate ZTE in joining Samsung, Panasonic, Lenovo, and Netgear as my list of manufacturers I'll never touch again. Making this list requires an exceptional dedication to releasing defective products and maintaining consistent customer deception about resolving problems.
Pretty sure it was a bad SD card.. Still had issues after complete rollback to Marshmallow.. Pulled the SD card out, working now.
Hi, first of all I apologise if this question has been asked but I don't know how to search just this place.
I'm using everything stock, no root, stock launcher.
I have my phone set up to ask for the password on reboot. I have my fingerprint reader set up to unlock my phone. I also have the fingerprint reader set up to wake the screen.
However under certain circumstances the fingerprint reader does not unlock the phone. The most reliable way to trigger this behavior is to plug the phone in to charge.
I exclusively lock the screen with the power button.
The fingerprint reader is still responsive and it still wakes the screen but there's no vibration feedback and it does not unlock. After I unlocked the phone with my password and lock it again the reader works again.
So what's going on here? How should I debug this?
After reboot it is normal to ask for password first time. Sometimes i have also seen this but when i unlock with pattern (my backup way) and lock again it works fine. I can not trace this to be related with charging or something else and it happens rarely but i have seen it also. Maybe a software bug.
Looking back to the days when i have LG V10 i remember that i had the same problem with fingerprint sensor not working sometimes. It was more frequently related to heat buildup as it was hot phone anyway.
I had the same problem these days, I think the fingerprint reader won't work if your hands are really cold.
Hmm I don't think my U Ultra is getting particularly hot and, no, my hands are certainly not very cold either. This behavior happens indoors.
It's just extra security plan and simple
Sometimes, not very often though, my fingerprint reader refuses to respond. Not even a misread where you get haptic feedback and not a lot else.
Just using the power button and entering my back up security (pattern in my case) and it comes back to life.
I don't particularly worry about it, but I suppose it's nice to see that it's not just me
Will see if the upgrade to 8.0 fixes it.
I met this problem.The solution was very interesting.I use Yandex.disk app.This problem did occur after the Yandex.disk app is update.I hard reset my phone.The problem was not in my phone.But I setup Yandex.Disk app the problem repeat occur.İf you installed Yandex.Disk, uninstall the application.if you don't use Yandex.Disk,The last apps update uninstall to try.
Good Lord I have so many apps installed though...
Then go to a full factory reset and see if it helps, thats the 1st thing you do when you have problem.
After a bit of experimentation this behavior seems to have stopped after I disabled/removed all Smart Lock Trusted Places -- a feature that is already known to be buggy.
I have it too, once a day it puts me to enter the password, its a security or a bug idk.
No more, no less, every time when its charging. I installed some 3rd party apps, its possible that they are to blame.
We will see when 8.o strikes and i will hard reset.
Garkan said:
I have it too, once a day it puts me to enter the password, its a security or a bug idk.
No more, no less, every time when its charging. I installed some 3rd party apps, its possible that they are to blame.
We will see when 8.o strikes and i will hard reset.
Click to expand...
Click to collapse
8 fixed this bug for me but i found more bugs in oreo so i am thinking to roll back to 7.0 and meet fingerprint sensor bug again because oreo problems are disgusting - car bluetooth does not works as it should - i can't read addressbook in my car head unit - it shows error. i found that is some bluetooth software parts was not included in 8.0 but successfully fixed in 8.1. and i'am pretty sure we will never receive 8.1 for u ultra.
in russian 4pda forum i found some reports (unconfirmed yet) that fingerprint bug disappeared. maybe somebody here can confirmed it?
No i have android 8 and issue still occurs sadly did not found a fix.
I've suddenly had this issue a couple of days ago a couple of times. I didn't do anything (except a couple of reboots) and it was fixed again.
Now after updating to Oreo and again using leedroids ROM, i didn't experience theissue again..
I talked to a htc representative and said to clear credentials from security/encryption and credentials seems to be a conflict in security certificates. For the moment it works.
So ,yeah ,I forgot the PIN code on my phone. I have an Asus Zenfone 3 Max ZC553KL and it does this strange thing every once in a while - it asks for my PIN code instead of my fingerprint reading when I try to enter my phone. It is absolutely adamant about it - no other options are available and I don't have an option to just recover/reset my PIN through my Google account or something like Samsung phones have. So ,of course this happens to me and I realise I have forgotten my PIN in the worst possible moment. Whatever has happened ,has happened ,but I believe my situation is a bit different that usual ,so don't just go ahead and comment I should factory reset my phone or something like that. I'm not giving up on my data.
So ,for some strange reason (totally coincidental) I have pretty much the exact same PIN on my laptop too (I just remembered that) ,but I also have a plethora of other sign-in options on my laptop so thankfully I'm not locked out of it as well. So I have been trying to brute force the PIN on my laptop hoping to find the right PIN and therefore unlock my phone as well. I wouldn't be able to do this on my phone since the amount of time I have to wait between tries doubles every 5-10 tries or so - from 30 to 60 to 120 seconds each time.
So ,the reason for my posting this in the first place is that I need suggestions and recommendations. Is there perhaps a faster way to do this? Should I try some other methods?
Currently I'm trying my hardest to remember some fragments of the 4 digit PIN's sequence and I'm 90% sure there are no repeating digits in the PIN. Tried around 90 combinations so far and I don't want to waste any more time if there happens to be a more efficient way.
FYI: My device is fully rooted and has TWRP custom recovery. One ,hopefully insignificant ,problem I have is that my phone's data is encrypted (I don't even know how I managed to root my phone having had this problem but it somehow happened). And what this means for me in the long run is that I cannot possibly backup any of my phone's data through TWRP or however else and thus my only option is no data wipe.
I will be giving up on unlocking it for today and start afresh tomorrow. Thanks in advance!
(I'm thinking of maybe trying out some brute force or dictionary attack type of method through some third party app on my laptop so I can figure it out for my phone. Dunno if that is even possible or feasible. Would be even better if I could just seen the PIN on my laptop since I'm already signed in but no ,why should it be easy.)