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
Related
Hi ! I purchased recently my Acer Iconia A500, and so far I'm very impressed with it. The only concern I have is this annoying sleep of death issue. It occurs to me like 3x a day, everyday ! I've tried everything written by the people (setting airplane mode, disabling wifi when screen blackens, update) but with no success.. anyone knows if this is going to be fixed in the 3.1 update or any update by Acer ? Anyone successfully managed to solve this problem ? Thanks !
Just to know.. I really wish that it's a software problem because I live in Brasil and bought it last week in EUA, so I won't be able to change it xP
As I mentioned in another thread, this has never happened to me. Not before or after the update.
The only thing I may do different from anyone else is I leave USB debugging turned on, I have a password login and as you mention I set the wifi profile to turn off when the screen goes off.
If this is happening 3 times or more a day, I'd highly recommend replacing the tablet. Yes, I know that's extremely inconvenient in your case...
But, have you tried a reset to factory defaults? It's worth a shot...
Prior to the 1.141-update my tab had that too, several times a day. I've put a WiFi-toggle widget on my desktop to be able to switch off WiFi before putting the tablet to sleep - that almost completely got riid of the inresponsiveness after sleep.
After the update to 1.141 there is no need anymore to switch off WiFi while sleeping, the update fixed that problem. But introduced a new one: when disconnecting the charger the tablet sometimes stops responding after about 1 minute and needs a reset.
I've had the 4.4.2 OTA about 2-3 weeks now, and for the most part its worked fine but as things go on I am noticing it starting to go a bit buggy. I have had issues with my Wifi, like this morning turned the phone on and it would not connect to my wifi, sure it saw it and it had full strenght but it would not connect to it, I went in manually and selected it nope nothing, I forgot network and connected again, nope nothing, restarted the phone nope, after 5 restarts it connected. I've also had issues with wifi connecting when coming out of airplane mode, everything else turns on but I have to mess around with wifi to get it going again.
Also had issues with apps crashing randomly, also had periods of sluggishness for no apparent reasons.
Anyone any ideas?
About the Wifi, try the Wi-Fi fix in this forum, maybe that'll help. For me stock is going absolutely fine. I was on OmniROM, but the updates start becoming a little buggy for me, so I switched back to Stock.
Anyone else having a similar experience and solution ? I have done a factory reset and have barely any apps. Basically when I leave it after using it I will return and be unable to turn it on. Nothing I do seems to be able to get it going again. I place it on the charger and come back a number of hours later and eventually I can get it to restart.
Not related to battery power level, and doesn't happen all the time.
Got mine today. Happened once so far. Just hold the power button for a while and it resets.
But, this better not be a daily problem.
You still have this issue?
Disable " lock on screen " option in launcher. That option give you ability tap twice to lock screen . Regurds
It only happened to me once first day, then i got two OTA updates, and it never happened again.
I have been using Yu Yureka for almost 9 moths now.
I was not having any other issue till last month.
But since last month, I am facing issues with my WiFi.
Few weeks ago, I was using my phone casually and everything was fine, but suddenly my WiFi got disconnected automatically. I just opened WiFi setting and seen that my router was visible.I just tried to reconnect it and it successfully got connected.
Then for some few days, this same issue was there. It just use to get disconnected oftenly.
But every time I open up my setting and after reconnecting it use to work fine.
Then after a couple of days later it as usually got disconnected and hence I opened settings again. This time, my router was not visible, even though the router was connected with my laptop.
So I rebooted my phone and got back to settings.
This time, WiFi was switched off and it was not turning on.
I tried to reboot my phone.
And after couple of reboot, it was switched on and I reconnect it.
It was annoying and I was fed up of this.
I was running official 5.0.2 cm12.
I choose to flash the latest official cm12.1 5.1.1 ,just because I thought it will help me out with this issue (yes my phone is rooted and have twrp installed).
After formatting my phone completely and flashing cm12.1 on cm12, I was hoping that now the issue will be gone but it was still there.
Conditions had gone worse.
Now it was disconnecting even more frequently.
So I decided to just wipe the system partition completely and install the ROM again.
I again flashed cm12.1
But condition gone worst.
Now at present,
My phone disconnects the WiFi as soon as I stop using the internet (as soon as phone stops receiving data from internet).
And once it disconnects, It doesn't show up any WiFi access point and I got to reboot the phone 3-5 times and there comes a reboot when the phone freezes for 5 seconds and again reboot 2 times by itself without me doing anything to it.
Then it turn on the WiFi automatically and I just have to go to setting to connect it to my router and it got connected.
If anyone have any solution regarding this issue, please help!
Facing the same issue, did you get any solution?
Head to service centre, I think its hardware issue not of software related.
Sent from my AO5510 using Tapatalk
Facing same pdoblem cannot be a hardware issue with multiple user showing same symptoms
Facing same problem
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.