I Got the update through a couple of days ago and I've had nothing but trouble since, lots of force quitting and locking up, the console has reset itself a few times as well.
I use the Shield with a 64gb Micro SD and a 500gb external Hard drive, I set the SD Card to act as internal storage, the setup worked fine but the Shield started to lock up so I took that out which fixed the issue. I did a factory reset on the console at this point as well.
Ive been able to setup the Sheild using the Hard Drive or SD Card as internal storage, that seems ok but at the minute the Google Play store wont stop Crashing. First thing I did after the restore was make sure the bundled apps were up to date, this I can do just fine but if I try to go into any app to download it to the console, I just get the 'Unfortunately Google play has stopped' error and nothing happens.
Ive tried resetting the console, clearing the cache on the store, trying the store before I update any bundled apps.. nothing works. The apps installed on there are fine but I cant add anything new.
Is anybody else having similar issues?
mozza54 said:
I Got the update through a couple of days ago and I've had nothing but trouble since, lots of force quitting and locking up, the console has reset itself a few times as well.
I use the Shield with a 64gb Micro SD and a 500gb external Hard drive, I set the SD Card to act as internal storage, the setup worked fine but the Shield started to lock up so I took that out which fixed the issue. I did a factory reset on the console at this point as well.
Ive been able to setup the Sheild using the Hard Drive or SD Card as internal storage, that seems ok but at the minute the Google Play store wont stop Crashing. First thing I did after the restore was make sure the bundled apps were up to date, this I can do just fine but if I try to go into any app to download it to the console, I just get the 'Unfortunately Google play has stopped' error and nothing happens.
Ive tried resetting the console, clearing the cache on the store, trying the store before I update any bundled apps.. nothing works. The apps installed on there are fine but I cant add anything new.
Is anybody else having similar issues?
Click to expand...
Click to collapse
I am having an issue when it wakes after sleeping, I get a message saying Nvidia HDMI Services has stopped working. If you click OK, it just shows the message over and over. The only way to get out of it, is to pull the power cord and reboot. Didn't have the issue until I upgraded to 6.0
gPhunk said:
I am having an issue when it wakes after sleeping, I get a message saying Nvidia HDMI Services has stopped working. If you click OK, it just shows the message over and over. The only way to get out of it, is to pull the power cord and reboot. Didn't have the issue until I upgraded to 6.0
Click to expand...
Click to collapse
I guess we need wait when official mm build shows up on Nvidia home page and then just clean install through fastboot. P.s. ...I have kind of weird lags with remote control, when I start using/presing buttons constantly - volume level goes up and down randomly, and also found even random woke ups from sleep.
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
I have three nVidia Shield 16GB versions and the one attached to a receiver gives me the "Unfortunately, NVIDIA HDMI Services has stopped." message every time I wake it from sleep (which you can click OK, but it immediately respawns). As was stated, the only option is to pull the plug. The other two don't have this issue and I'm wondering if it has something to do with being attached to a receiver. I've had zero issues until the 6.0 update.
stazna01 said:
I have three nVidia Shield 16GB versions and the one attached to a receiver gives me the "Unfortunately, NVIDIA HDMI Services has stopped." message every time I wake it from sleep (which you can click OK, but it immediately respawns). As was stated, the only option is to pull the plug. The other two don't have this issue and I'm wondering if it has something to do with being attached to a receiver. I've had zero issues until the 6.0 update.
Click to expand...
Click to collapse
I have a 16GB Nvidia Shield TV plugged directly into my Sony 4K television. Since the 3.0 firmware/Marshmallow update, I am getting the same "Nvidia HDMI Services have stopped" error as described above. And yes, pulling the plug is the only solution.
Yup. Mine is plugged into a Sony receiver. The irony is that this build was supposed to include a bug fix that people with Denon receivers were having. Well if they fixed that issue they apparently broke the rest of us! Face Palm
I have 2 shields, the one connected to a 4k TV has the HDMI service problem and the one on a 1080p TV don't. I switched both and problems persisted on the 4k TV.
I don't pull the plug to reboot. I just hold back to make the power menu open. I press OK and spam the down button to get on the reboot option and the just spam the OK button for the reboot.
Very annoyed by this.
Contacted Nvidia support about this "HDMI services have stopped" issue: useless. They just provided a generic power cycle/ reboot troubleshooting procedure...which didn't work anyway.
Sent from my Nexus 6P using Tapatalk
same here
mozza54 said:
I Got the update through a couple of days ago and I've had nothing but trouble since, lots of force quitting and locking up, the console has reset itself a few times as well.
I use the Shield with a 64gb Micro SD and a 500gb external Hard drive, I set the SD Card to act as internal storage, the setup worked fine but the Shield started to lock up so I took that out which fixed the issue. I did a factory reset on the console at this point as well.
Ive been able to setup the Sheild using the Hard Drive or SD Card as internal storage, that seems ok but at the minute the Google Play store wont stop Crashing. First thing I did after the restore was make sure the bundled apps were up to date, this I can do just fine but if I try to go into any app to download it to the console, I just get the 'Unfortunately Google play has stopped' error and nothing happens.
Ive tried resetting the console, clearing the cache on the store, trying the store before I update any bundled apps.. nothing works. The apps installed on there are fine but I cant add anything new.
Is anybody else having similar issues?
Click to expand...
Click to collapse
gPhunk said:
I am having an issue when it wakes after sleeping, I get a message saying Nvidia HDMI Services has stopped working. If you click OK, it just shows the message over and over. The only way to get out of it, is to pull the power cord and reboot. Didn't have the issue until I upgraded to 6.0
Click to expand...
Click to collapse
I have the HDMI issue upon waking from sleep, going through a Yamaha surround amplifier. Never had the issue before update. I also cannot do anything with the play store, selecting anything in the store brings up the unfortunately plat store has stopped. Called Nvidia and spoke to tech there, no help thus far, we have a thread in the nvidia forums about the play store. Called google, and they refused to even speak to me because they say it's a manufacturer's problem. Please report to our forum at the nvidia site, there are many of us there and we have tried almost everything to no avail.
Here's the link to the Nvidia forum. https://forums.geforce.com/default/...le-play-store-not-working-with-new-update-/9/
So this Nvidia Shield TV v3.0 firmware/6.0 Android update when about as bad as possible short of bricking everyone's box.
So far I'm seeing in the forums from other owners:
New "Nvidia HDMI Services Have Stopped" error message that can only be addressed by power-cycling
Shield not powering on from Sleep
Google Play Store broken/crashing
Shield controller mis-behaving
Netflix app dropping frames during playback.
Various issues with storage
And I'm sure many others I'm not aware of.
This has been compounded by the Kodi v16 update that just came out and broke 4K playback which is now being resized to HD resolutions.
I have not had any problems with my shield and this update. But must admit that I have not used it that much since the update.
Btw. As far as I can read on the Nvidia shield forum, choosing an SDcard as internal storage, will overwrite use of the internal storage for apps and games.
All the same problems on mine as well. Wish I didn't update!
16g model. I have not had any power cycling or app crashing or services stopped issues. But once again, they've clearly changed how bluetooth works, because sixaxis is currently non functional, which I loathe. Ever since the console came out, the DS4 controller has worked better than Nvidia's own controller, regardless of previous bluetooth issues. Makes me wonder if Nvidia targeted it for convenience.
I have an Android TV Shield (v3.0) which is connected via an amp Denon April-x4100w (hdmi back cover). The first day everything was fine, the second day more image. I tried restarting the shield, reset the amp, turn off the upscaling of the amp, change the video frequency .... do you have a solution???
"NVIDIA HDMI Service stopped" (NVIDIA HDMI Service wurde beendet"
gPhunk said:
I am having an issue when it wakes after sleeping, I get a message saying Nvidia HDMI Services has stopped working. If you click OK, it just shows the message over and over. The only way to get out of it, is to pull the power cord and reboot. Didn't have the issue until I upgraded to 6.0
Click to expand...
Click to collapse
So to say, I am glad not being the only one having that big issue with the NSATV.
Since the update to FW 3.0 (Android 6.0), I often have the problem that I get the pop-up "NVIDIA HDMI Service stopped" (as my NSATV is set to German language it is "NVIDIA HDMI Service wurde beendet").
Even if I accept by clicking "OK", nothing changes. The pop-up doesn´t disappear and I can´t do anything else.
I need to plug-off from power to restart it completely.
Any idea or workaround known?
May be it can be solved by using a different power-off or sleep-mode as before?
Appreciate any idea and help as it is not really amusing to plug-off the NSATV every time..
Dietmar
realcams said:
Since the update to FW 3.0 (Android 6.0), I often have the problem that I get the pop-up "NVIDIA HDMI Service stopped" (as my NSATV is set to German language it is "NVIDIA HDMI Service wurde beendet").
Even if I accept by clicking "OK", nothing changes. The pop-up doesn´t disappear and I can´t do anything else.
I need to plug-off from power to restart it completely.
Any idea or workaround known?
Click to expand...
Click to collapse
I'm having this same exact issue, and have been for a couple weeks (since the update). I've even searched to see if there is some way to go back to the previous version. I don't have a nandroid backup or anything (wish I had thougth ahead), but does anyone know if there's a way to rollback to the Lollipop stock release (including any firmware/boot/etc)?
It will only crash HDMI if unit was sleeping. If you power off instead, it will not happen. Only caveat is that you can not wake the device with controller or remote and have to manually touch the shield unit and wait for the android to load. Not ideal but manageable.
My Shield TV is not usable anymore. Right after a reboot the desktop/home screen is freezing. The spinning circle while loading recommendations stops spinning and the Shield TV does not react to any input. Even the clock is not counting anymore. After about 5 minutes the Shield TV reboots itself (watchdog reset?). And again keeps freezing as soon as the home screen appears. This sucks.
I take it that the general consensus is not to upgrade to FW 3.0 whatsoever? I just received my Shield today, and I'm a little hesitant to even power it up
Related
There are some threads indicating this is a problem after the leaked update. I did the official OTA update today and immediately ran into the issue. After doing a factory data reset to make sure i cleared any possible cob webs out the issue was still there. Tablet runs fine while in use, as soon as it goes to sleep it reboots.
I removed the sd card that was installed and the problem went away. Wondering if anyone can confirm......
jhoelz said:
There are some threads indicating this is a problem after the leaked update. I did the official OTA update today and immediately ran into the issue. After doing a factory data reset to make sure i cleared any possible cob webs out the issue was still there. Tablet runs fine while in use, as soon as it goes to sleep it reboots.
I removed the sd card that was installed and the problem went away. Wondering if anyone can confirm......
Click to expand...
Click to collapse
I had the issue initially with the leaked 3.1. I factory reset, wiped caches, and it seemed to go away. About 30 minutes ago, it happened again. BTW, I am on PRIMORDIAL.
Questions for you:
Was the tablet docked at the time (mine was each time)?
Your SD card...are you talking about the miniSD or SD in the dock (I had a mini in the tablet, and SD in the dock)?
What is the brand of the SD card (I have a 16 GB AData micro, and a Patriot Class 6 SD in dock).http://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=14345447
Hopefully we can nail this down. Didn't see the issue at all in 3 weeks on 3.01 (Prime), FWIW.
jhoelz said:
There are some threads indicating this is a problem after the leaked update. I did the official OTA update today and immediately ran into the issue. After doing a factory data reset to make sure i cleared any possible cob webs out the issue was still there. Tablet runs fine while in use, as soon as it goes to sleep it reboots.
I removed the sd card that was installed and the problem went away. Wondering if anyone can confirm......
Click to expand...
Click to collapse
I have the same issue after installing the "Leaked 3.1 update". It was fine without docking to keyboard dock. I used the tablet itself for one whole day without any reboot. The last few days I noticed that it automatically reboot while in sleep mode as well (while docked to keyboard dock). It happened three to four times yesterday and three times today...
I tried to downgrade from 3.1 to 3.0.1 again this morning (using the official 3.0.1 from Asus website). After downgrading I was getting constant "Force Close" error messages. My tablet was totally useless at that point. I was not able to go into "Recovery Mode" to do a data wipe or factory reset. Only way to recover from this was install the "Leaked 3.1 update" again. I am still having automatic reboot issue with this Leaked 3.1 update. I did not do any cache wipe or factory reset yet. I do not want to reinstall and recofigure all of my apps and emails again...
jhoelz said:
There are some threads indicating this is a problem after the leaked update. I did the official OTA update today and immediately ran into the issue. After doing a factory data reset to make sure i cleared any possible cob webs out the issue was still there. Tablet runs fine while in use, as soon as it goes to sleep it reboots.
I removed the sd card that was installed and the problem went away. Wondering if anyone can confirm......
Click to expand...
Click to collapse
I have had the same issue since I installed 3.1 leaked. Symptoms same as above, whereas my tabelt only reboots while docked and after it goes to sleep. I just removed both my external cards to see if that changes anything. I have a Sandisk mircosd HC 16gb in the tab and a Centon SDHC 16gb in the docking station. Hopefully we can nail this down.
Please let us know if you removed your micro of SD in docking station that solved the issue.
Thanks!
After my official OTA update I have noticed my tablet reboot itself in sleep mode at least three times, and those are the times that I saw. Of note, it WAS NOT docked into the keyboard when it rebooted two of the times, and it might have been docked one of the times. Also, I don't have an SD card installed on mine. I'll let you know if the problem persists.
update! I have removed my sdcard from my keyboard dock and so far, no reboots while docked. Please post if this has solved anyone else's reboots.
Thanks!
Sent from my Transformer TF101 using XDA Premium App
So, as I suspected. I too have not had the issue since removing my SD card from the dock 2 days ago. I am 100% convinced at this point that the culprit is here, whether it is a bug in 3.1, compatibility with my brand of SD card, or both.
I did not see reboot after I removed my sd card from my keyboard dock... but I found something suspicious: When my TF is docked to keyboard dock, I will put it to sleep... after few minutes of in-activity, when I tried to wake up the TF... It would not respond. About 30 seconds to 1 minutes later, I will see an Asus logo come up and it goes into the lock screen. I checked my system "up time", it still shows over 20 hours of up time... Really strange... I thought that whenever you see the Asus logo on your screen it means it's booting up or something... Have anyone else seen this happen before? I never seen this happen in android 3.0.1.
mikewong27 said:
I did not see reboot after I removed my sd card from my keyboard dock... but I found something suspicious: When my TF is docked to keyboard dock, I will put it to sleep... after few minutes of in-activity, when I tried to wake up the TF... It would not respond. About 30 seconds to 1 minutes later, I will see an Asus logo come up and it goes into the lock screen. I checked my system "up time", it still shows over 20 hours of up time... Really strange... I thought that whenever you see the Asus logo on your screen it means it's booting up or something... Have anyone else seen this happen before? I never seen this happen in android 3.0.1.
Click to expand...
Click to collapse
Never mind... My TF rebooted three times today while docked on the keyboard dock... This is when I already removed the external SD card on my dock...
I'm wondering if using the custom rom will resolve this issue?
I noticed that there are two ramdump files create today after my TF randomly reboot. I opened up the .log files in windows and noticed the following error messages:
<0>[102067.945373] Internal error: Oops: 817 [#1] PREEMPT SMP
<0>[102067.945409] last sysfs file: /sys/devices/platform/tegra-i2c.1/i2c-2/2-0019/power_supply/dock_battery/status
I have no idea what this means...
Mike
This is exactly why I always wait a couple months before upgrading. Let all you guinea pigs do everything for me first.
What the hell is wrong with these mega companies? Don't they test their own freakin' devices? It's really simple. Before you release an update, test it on your devices first in different situations. It's like asus didn't even bother to do test runs before they released this update.
Unrooted TF here. I always have it docked. Installed the official upgrade as soon as it was available. Played on the tablet for a while, ran a speed test and closed the lid. We've been busy the last couple of days, but after reading about the reboot prob, I opened the tablet every so often to see if I was having the same problem. It was always at the speedtest app, and I simply closed the lid. I'm assuming it never rebooted if it was always at the speedtest app.
Today, I opened the lid, still at the speedtest. I hit the home key, forgot what I did, but it rebooted.
My long-winded point is, does the reboot only happen at the Home screen? I find it odd that for several days this was fine sitting with an app open.
I have a unrooted TF and i just updated on Saturday. I know of 1 reboot (docked w/ sd micro card in) but I also saw a 20% battery drop while closed.
Same issue here
Unrooted Leaked 3.1
MicroSD 32GB Sandisk Class 6
SD In Dock 32GB Class 6 Microcenter Brand
Loaded apps after a hard reset post 3.1, maybe 20 or so apps installed, still observed
the reboot issue, I could be sitting in pandora or slacker and it would reboot.
It would also reboot just sitting at the home screen.
I have hard reset again from the boot loader and have not installed anything, only have gmail configured.
I have removed both flash cards and I will see what happens.
I like 3.1 but this is a PITA.
G
Earlier today, a few apps on my Nexus 7 have just started closing within one or two seconds of opening them.
Google Search Bar, Facebook and Catch Note all close within a couple of seconds after opening them. I have used them fairly frequently for the last few weeks with no problems. Other apps, such as Twitter, Chrome and some games all work fine.
I have turned my device on and off a couple of times, but the problem still persists. Any ideas?
The problem is still occurring for me.
Gmail, Calendar etc... all also closing within a second or two of opening. Is this a common problem?
Is your N7 all stock or do you have a custom rom?...custom kernel?
You really need to provide some information in order to get help.
I haven't seen it in the OP so: Reinstall them
Visa Declined said:
Is your N7 all stock or do you have a custom rom?...custom kernel?
You really need to provide some information in order to get help.
Click to expand...
Click to collapse
I haven't rooted my Nexus, or anything like that, it's all stock.
I just uninstalled Facebook, then downloaded it again. It seems to be working. Other apps still have the same problem. I assume that I have to do the same for all other apps - but is that even possible for apps such as Gmail, Calendar and the Search Bar?
Uninstalling and re-downloading hasn't worked as I had hoped.
It seems to have worked for Facebook. But I did the same for Catch Notes, and although it worked for a minute or so when setting it up, after creating a test note, it force-closed, I opened the app up again, and the old problem of closing within 2 seconds happened.
Other apps such as Gmail, I uninstalled, 'updated' again, and nothing changed, still closes immediately. There is no error message, it just returns to the home screen.
I thought that Task Killer might have been a problem, but I uninstalled that, restarted the Nexus, and the problem persists. Actually, when I turned off my Nexus, and tried to turn it back on, it was stuck on the 'coloured X' screen for a few minutes, I had to hold the power button down, and turn it on again. I'm starting to worry about my Nexus now.
Update:
A couple of other odd ones.
Google Drive doesn't even open. When clicking on the icon, the normal shading effect happens, but nothing else, no window even for a second.
Google Calendar opens, and just has a white screen, as if it is ready to load the calendar, but nothing loads. It doesn't close, just remains on the white screen, which can't be backed out of without pressing the home button.
Have you tried doing a cold-boot on the device? Maybe another app running in the background is causing conflicts. Where there any recent apps that you've downloaded?
Asus_USA said:
Have you tried doing a cold-boot on the device? Maybe another app running in the background is causing conflicts. Where there any recent apps that you've downloaded?
Click to expand...
Click to collapse
I have just followed the instructions for a 'cold-boot' and now my Nexus can't get beyond the 'X' screen...
I have held the power button down a number of times, and tried turning it on again - but the 'X' continues to be displayed for over 20 minutes.
Just managed to turn my device on - but the problem still exists.
I didn't download any new apps that seem to have caused this problem. Though I think an app might have force closed and the Nexus displayed an error message such as "android/Google system stopped working" (probably different) and my home screen went blank for a while. Everything reappeared though after a short while. It could have stemmed from that.
Sorry about another bump, but i'm wondering if anybody has any more ideas before I go for a factory reset?
Edit: Actually, I think that I have found the cause of the problem. I just opened a game (Let's Golf 3) that I was playing before the problem started and after a few seconds, a message popped up saying "Unfortunately, Launcher has stopped". When I press OK, it returns after a few seconds.
I pressed the sleep button, and my Nexus turned off. Now trying to turn it on again, having some problems getting past the 'X' screen again. If I finally get in, should I uninstall the game? Any other solutions to this problem?
If your N7 can boot up, go the isolate & identify routines - disable/uninstall or freeze the golf game - do a normal shutdown/restart.
If normal functionality is back, you've just found the source. Not a gamer myself except for Angry Birds ... , but from the Play Store description, it access & make changes to system & protocol, etc. as you should contact/email golf's tech support for resolution. Otherwise, take a look of any background running apps or widgets, newly added or updated.
Letitride said:
If your N7 can boot up, go the isolate & identify routines - disable/uninstall or freeze the golf game - do a normal shutdown/restart.
If normal functionality is back, you've just found the source. Not a gamer myself except for Angry Birds ... , but from the Play Store description, it access & make changes to system & protocol, etc. as you should contact/email golf's tech support for resolution. Otherwise, take a look of any background running apps or widgets, newly added or updated.
Click to expand...
Click to collapse
Thanks for the help.
I couldn't get my N7 to boot up, so I finally gave in and did a hard reset (by holding power + volume down, Recovery Mode, then wipe data etc...) but my N7 still won't boot up
I have wiped it twice, and rebooted it, yet it is constantly stuck on the 'X' screen. What on earth can I do?
Gawge said:
Thanks for the help.
I couldn't get my N7 to boot up, so I finally gave in and did a hard reset (by holding power + volume down, Recovery Mode, then wipe data etc...) but my N7 still won't boot up
I have wiped it twice, and rebooted it, yet it is constantly stuck on the 'X' screen. What on earth can I do?
Click to expand...
Click to collapse
I would flash the stock system image.
Sent from my Nexus 7 using Tapatalk HD
korockinout13 said:
I would flash the stock system image.
Click to expand...
Click to collapse
How would one do that?
My N7 isn't rooted or unlocked.
Gawge said:
How would one do that?
My N7 isn't rooted or unlocked.
Click to expand...
Click to collapse
You will need to download the factory image, unlock your bootloader, and flash it. There is a guide on this forum, it might be stickied.
Sent from my Nexus 7 using Tapatalk HD
I was hoping there was going to be a resolution to this other than a "flash to stock" suggestion... My Nexus started doing this exact same thing this past Sunday when it ran out of power completely and needed to be recharged. After it powered back up from charging the following apps quit working altogether or just started quitting once it appears they try to access data: Netflix, Currents, Zillow, Gmail, HBO Go, Press (though Google RSS Reader works), NVision, TegraZone and a couple others. I have done the reboot thing as well and almost had this thing brick again (stuck at X), but I managed to clear the data cache from the fastboot menu and it started up again. I'm now at the point where I'm troubleshooting individual apps but the clear data/cache, uninstall - reinstall process isn't working for any of the broken apps. This is now the 4th time I will be facing a 'flash to stock' situation as it appears that I've had every problem that leads to this 'fix'. I'll try a couple more things (mostly deleting and clearing everything) but I'm really frustrated with how many times I've had to flash this damn thing. sigh.
Running: Everything stock - just got this two days ago. Have a wireless Xbox 360 controller attached which works just as well as the gamepad that came with it.
It seems every other game (or more) that I install from the play store launches and then gives me a screen where the gamepad just plain doesn't work. At all. Both of them. It's driving me mad. I just hit the circle to go home and launch another game and a grip of games do work...but many don't...
Other issue - possibly causing it: Google Play Games fails to find my Google+ profile.... no damn clue why, it complained the first time that I didn't have one, I went and made one with just default crap, but everytime it launches (which most games launch it) it just says "Need Public Google+ Profile->Cancel or Proceed", proceed just pops it right back up until I cancel because it can't find it...
Has anybody run into either of my issues? Any ideas?
How do you get the wireless 360 controller working with the shield ?
tillaz said:
How do you get the wireless 360 controller working with the shield ?
Click to expand...
Click to collapse
I just connected the wireless dongle, and it worked automatically... The controller's little light constantly blinks like it can't figure out if it's first or second player or whatever, but it works flawlessly. Works even when the wifi-pairing for the shield controller doesn't work.
This device seems awesome save for the endless bizarre ass **** that don't seem to be working correctly...
Trying a factory reset right now by booting with computer plugged in->Hold power for 4 seconds->Choose "Boot recovery kernel"-> get "No Command" image with android laying down and his belly open. Hold power button for some period, and recovery menu came up; wiped cache, then chose wipe data/factory reset. It immediately went back to the "No command" picture. I presume it's wiping.... It's a 16gb model so hopefully shouldn't take hours..
Will see if in a couple hours it's still staring at me like a dying android proclaiming "No Command", then I'll presume the wipe data didn't actually wipe ****.
Would sure like to get that recovery.zip on the shield root thread, but it's undownloadable-> Goes all 1kb/sec then the download just cuts out...
I keep having to reconnect my previously paired bluetooth devices, and I believe this started after upgrading to Marshmallow. Initially, my devices seemed to unpair infrequently, like maybe every 10-14 days. But now, for whatever reason, it is happening more frequently and sometimes daily.
After reading through the forums here and at AC, I thought it might be happening because I rename the devices after I pair them, but that didn't solve the problem when I stopped that.
After Marshmallow, Android Pay required a screen lock to use, which I never had done in the past, so I also enabled Smart Lock and set my paired bluetooth devices as trusted devices. I just disabled all of that (screen lock, android pay and smart lock) so I maybe that will solve the problem, but I suspect it won't.
Anybody have any ideas?
Hi,
I have the exact same issue!
VEry annoying!
Clearing, hard reseting, repairing etc... tried EVERYTHING!
Now i also set smart lock and trusted devices.. Will go to a meeting and back, will test it on the way.
magdan83 said:
Hi,
I have the exact same issue!
VEry annoying!
Clearing, hard reseting, repairing etc... tried EVERYTHING!
Now i also set smart lock and trusted devices.. Will go to a meeting and back, will test it on the way.
Click to expand...
Click to collapse
Well, that didn't work for me. I also tried clearing the cache from the boot menu, but it's still dropping my paired BT devices.
My new Square Up Contactless + Chip credit card reader arrived yesterday. Unlike their previous credit card readers that connect through the earphone jack, this one connects through BT. I cannot get it to connect to my XPE, but am able to connect it to my Moto X 2nd Gen.
I really hope this is a Marshmallow issue that will be fixed soon, but the lack of responses has me concerned that it won't.
I tried resetting the network settings and wiping the cache, neither of which fixed it. I decided it was time to do a full factory reset, but that didn't fix it either. Any other ideas?
I going to assume you are unrooted... But either way if you can change your SELinux to permissive that might help your Bluetooth issue there is this app here that might help out
https://www.dropbox.com/s/xdllg9xxodnib77/com.mrbimc.selinux_42.apk?dl=0
Sent from my XT1575 using Tapatalk
Got the new phone from Motorola a couple of days ago. After reinstalling all my apps and customizations, including renaming my device and the 4 Bluetooth device I connect to, I started to experience the same problem. Not initially, but soon after I turned on the new System UI Tweak option.
So, I turned off the feature and it hasn't happened since. It has been a few days and I have restart (soft reset) several times, which I found would usually trigger the loss of pairing, so I'm keeping my fingers crossed that it was related to the UI tweaker.
I'm trying to diagnose a frustrating problem with my girlfriend's Samsung T580 tablet that started occurring a few days ago - basically random apps crash on reboot. Unfortunately these are key apps like Google, Google Play Services and a variety of other key services. The Google service for example will just crash in a loop.
She does not remember installing any non-automatic OS update although I believe one has been recently.
Tablet: Galaxy Tab A SM-T580
Build: M1AJQ T580XXS5CTD1
Android Patch Level: 1st April 2020
I've gone through a number of steps to try and resolve it, increasing in severity
1. Cleared the user cache
2. Did a factory reset - logging into the same Google account
3. Did a factory reset - and did not sign into any accounts
4. Used Odin to reinstall the latest firmware5
5. Tried to use Odin to reinstall an older firmware - but was prevented as Odin cannot downgrade the bootloader
I'm out of ideas and I'm starting to think it might be a hardware fault or some serious corruption behind the scenes.
I've had a look at an ADB log but I cannot be anything obvious - would anyone with more experience in reading these things be able to see if they can tell anything? I've attached.
Any other suggestions for how I can bring this back to life?
Thanks in advance
Today I rooted this, installed TWRP and installed LineageOS - and the crashing apps is still happening (even on the setup screen just after a factory reset)
My only conclusion is that somehow the storage or RAM is damaged which is causing the random crashes - so the tablet is beyond saving
pryonic said:
Today I rooted this, installed TWRP and installed LineageOS - and the crashing apps is still happening (even on the setup screen just after a factory reset)
My only conclusion is that somehow the storage or RAM is damaged which is causing the random crashes - so the tablet is beyond saving
Click to expand...
Click to collapse
I think you are probably right but I do have a couple of suggestions. First, does it have an external SD card? If so, have you tried removing it? Second, does it still crash with the power cable plugged in? The T580 is known for having problems with the ribbon cable connector on the battery. If it is intermittent, it could cause crashes. In fact, it could still do it with the charger plugged in by causing spikes, but if it doesn't crash when plugged in, you know it's a battery problem.
lewmur said:
I think you are probably right but I do have a couple of suggestions. First, does it have an external SD card? If so, have you tried removing it? Second, does it still crash with the power cable plugged in? The T580 is known for having problems with the ribbon cable connector on the battery. If it is intermittent, it could cause crashes. In fact, it could still do it with the charger plugged in by causing spikes, but if it doesn't crash when plugged in, you know it's a battery problem.
Click to expand...
Click to collapse
Many thanks for the suggestion - alas I tried it and it's still doing the same thing. Looks like a hardware fault of some sort