I have an Explorist Gen 4 that I've started having issues with. It's practically brand new although I hadn't used it for 6 months or so. I've got a Oppo Reno 2 running Android 10.
First issue is that touch seems to start having issues after the watch has been on for 30 mins or so. I can touch to wake it up, but then any touch/scrolling does not seem to register from then. If I restart it, all is normal again for a little while, so I think this is a software thing.
So I tried resetting the watch and reconnecting it to my phone, but it just won't connect any more. Most of the time the watch says it's connected, but the phone sits on popup showing the bluetooth pin.
Sometimes the watch gets stick on "Oppo would like to connect".
Sometimes the watch says connected and the watch is in the list of bluetooth devices, but wear os doesn't see it as connected.
The whole thing seems to be a mess.
Anyone seen any of this before, or have any ideas?
Edit:
OK, so I managed to get it to connect after messing about and adding it to bluetooth manually (which is not meant to work).
But the swipe/touch issue after a period of time is still an issue. It's pretty much only as good as a regular watch right now.
Related
Hello,
ok, I gave up on moving APPs to external SD on ICS 4.0.3...
Here is my new issue in a nutshell....
I updated to ICS 4.0.3 with no problems and everything worked fine for months. Within the last month, the tablet has developed a random problem, usually 30-90 seconds after it boots, where it may or may not freeze up (i.e. the screen is unresponsive) and I have to turn it oss and reboot and hope it doesn't happen again.
Sometimes this happens one or two times in a row and then its fine, sometimes it will happen five times or more, and then the next boot it is fine, sometimes it works fine on the first boot.
I have removed all kinds of apps and media to make sure I have lots of room and curently have about 5G free. but that didn't fix the issue.
I looked into the GPS txt files being left behind and made sure they are removed regularly, but that doesn't help the issue.
I used a Device Info APP to display what is going on when this happens, and while it doesn't show any APP or process I can see as the culprit, the CPU is being maxed at 100%?
It also seems to have "something" to do with the WiFi, as when it "locks up" the WiFi icon in the tray goes away and when I go to settings it seems stuck trying to turn off the WiFi. But at other times then the WiFi is working fine?!
Also, sometimes if I let it go to sleep for too long, when I wake it up this will happen..
SO... anyone got a clue what this could be?!
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.
Since updating to 8.0, my shield pro (2015) keeps freezing for a while (15 seconds to a few minutes) and the controller turns off after about 30 seconds of inactivity (vice before when it would stay on for a few minutes before turning off).
Has anybody else witnessed this behavior?
Cheers,
B. D.
The wifi on mine will magically turn itself off and won't restart till I restart the device..
Sent from my ONEPLUS A5010 using Tapatalk
I use Ethernet so sorry cant say if mine does that, however I have been having an issue since update that Netflix will not exit when i click exit from within the app im not sure if this is a Netflix or a shield thing but it started after the new update has anyone else had this issue or other issues?
My sheild could not pass through the connect to wifi stage. I tried several ways even using google nothing seem to work. It displays "cannot reach internet" it has been stuck on the setup since the update. I'm so tired dont know what else to do.
On my 2015 16Gb, after I put the device on sleep, I can not turn it on. I have to unplug it or sometimes only to manually touch the device.
Does anyone experience the same problem?
Lasted a couple of days on 8 before downgrading back to Oreo. Very unstable, and the killer for me, no root.
Wifi & bluetooth problems here too. Worked for about 1 minute and disconnect. What can I do? Reset the shield, recover the shield with 8.0, reboot router. No idea what I can do
Hello,
I would like to ask question, hoping someone will be able to help me solve this problem.
I have the fossil 5 garrett and somehow i stop getting the notification although everything is setup well at the phone and the watch.
The only thing that solve this problem is Uninstall the wear os in my phone and install it again, but then again after one or few days the notifications dissappear again.
It doesn't make sense to Uninstall and install the wear os every few days. I thought maybe it's something with the app power setup and i changed it to manually so the app will work all the time but still i dont get the notifications at the watch.
Do you have any idea what can cause this problem of notification dissappear?
Thanks,
Nessi
My Fossil Gen 5 also loses notifications at times, seemingly if it hasn't undergone a restart after a few days. It sometimes auto-restarts when placed on the charger. A small inconvenience, but this keeps it working well. For restart, press center crown button for Apps, then Settings, scroll for Restart.
My Fire HD 8 tablet got a forced FIre OS update from Amazon a couple of days ago, and I was surprised to see that it jumped from 6.3 to 7.3.1.6. Apparently Fire OS 7 is based on Android 9 (Pie).
Unfortunately the update brought the usual bunch of screwups:
- Most of the tablet settings reverted to default, and it has taken a lot of time to correct them all as issues arise.
- Many components and apps did not update automatically to match, and had to be updated manually.
- I was left with one item stubbornly stuck in the Download Manager queue that wouldn't go away or stop notifying me - the U.S. English Dictionary. After clearing the queue, clearing data and cache for the download manager, and rebooting several times, I finally found a place I could do a manual update of the dictionary several levels deep in the keyboard settings. That seems to have fixed it. Not a good design.
- Show Mode is broken. The tablet will still enter Show Mode and work for about 20 minutes or as long as the screen is active. But it now drops out of Show Mode just a few minutes after the screen goes to sleep, every time. I'm accustomed to it dropping out of Show Mode from time to time, but it's now unusable because of this. And that's not the only issue - the feature to automatically wake the Show Mode screen when the camera detects movement has stopped working after the update.
The issue of it dropping out of Show Mode was the most annoying. I tried everything I could think of that might affect it, and I finally hit on the cause by process of elimination: it's Bluetooth. The tablet is normally connected to a nearby Bluetooth speaker in Show Mode. That still works, but since the update it's causing the tablet to constantly drop out of Show Mode. If I turn off Bluetooth, the tablet stays in Show Mode. I suspect that this is a power management issue - somehow since the update reset all the settings, the tablet reverted to powering down Bluetooth after 20 minutes, and there's a bug that causes it to drop out of Show Mode when that happens. I went through all the settings related to power management, but no luck finding anything that apparently affected it. I even went to the trouble of creating a Tasker task to activate the Bluetooth audio every 15 minutes as a preventative measure. That was effective in preventing the tablet from dropping out of Show Mode. And then a day later I shut that Tasker routine off as a test, and the tablet stayed in Show Mode anyway! Somehow after enough time and enough reboots, the problem fixed itself.
Better luck on the camera motion-detection front - it started working again after I went through all the settings and flipped them back and forth to make sure they were set correctly. There has always been a bug in Show Mode that it has a fixed camera sleep period of 10pm to 7am, and Amazon forgot to provide a setting to change it (it's not the same as the Do Not Disturb setting). I suspect that the camera was stuck in sleep mode until I flipped all the settings back and forth.
DJames1 said:
My Fire HD 8 tablet got a forced FIre OS update from Amazon a couple of days ago, and I was surprised to see that it jumped from 6.3 to 7.3.1.6. Apparently Fire OS 7 is based on Android 9 (Pie).
Unfortunately the update brought the usual bunch of screwups.....
Click to expand...
Click to collapse
My tablet gets stuck in a bootloop after doing the update. Previously, I was on Lineage but restored it back to the previous OS6 version - now any time it does an update, i have to revert back to an old stock. Anyone have a suggestion?
Your Fire tablet is updated forcefully without your interaction. You can use a firewall to block these crappy and spammy updates.