Yesterday I used my chromecast again. .... after using it when using notification shade a persistent error appears. ... only way to fix it is rebooting. Any ideas?
Enviado desde mi SM-P600 mediante Tapatalk
Can you elaborate some more? I'm not having any issues like yours so give some extra information please.
mantrajt said:
Yesterday I used my chromecast again. .... after using it when using notification shade a persistent error appears. ... only way to fix it is rebooting. Any ideas?
Enviado desde mi SM-P600 mediante Tapatalk
Click to expand...
Click to collapse
Seems a few of us are waiting for this to be fixed. Another forum member has sent their tablet back to samsung twice now hoping for a fix. This problem is apparent on my note pro as well, so I think we need sammy to push us a software fix
chgambini said:
Seems a few of us are waiting for this to be fixed. Another forum member has sent their tablet back to samsung twice now hoping for a fix. This problem is apparent on my note pro as well, so I think we need sammy to push us a software fix
Click to expand...
Click to collapse
Hope this doesn't take them soooo looooong
Enviado desde mi SM-P600 mediante Tapatalk
I wonder if the Samsung phones running 4.4 have this too or is it just the tablets? I know the 12 inch version has this issue too.
It's the primary reason I'm still running 4.3.
chgambini said:
I think we need sammy to push us a software fix
Click to expand...
Click to collapse
Not to be the bearer of bad news but if it's an isolated problem affecting a small percentage of users the likelihood of Samsung issuing an update for just this specific issue is pretty slim. I don't use Chromecast myself but I was at a friends house last night and tried it from my N10.1-14 running 4.4. I didn't have any issues and the notification panel didn't bork while I played with it during Chromecast playback. Since those with the issue didn't have it on 4.3 it's obviously a s/w compatibility issue or conflict. I'd try to narrow down what's unique on the Pro's and Note's running 4.4 that are having problems to find the ROM version/region, installed s/w, combination of s/w, configuration, or settings that are causing it. You guys huddling together to figure it out will be faster than waiting for a fix that may never come.
BarryH_GEG said:
Not to be the bearer of bad news but if it's an isolated problem affecting a small percentage of users the likelihood of Samsung issuing an update for just this specific issue is pretty slim. I don't use Chromecast myself but I was at a friends house last night and tried it from my N10.1-14 running 4.4. I didn't have any issues and the notification panel didn't bork while I played with it during Chromecast playback. Since those with the issue didn't have it on 4.3 it's obviously a s/w compatibility issue or conflict. I'd try to narrow down what's unique on the Pro's and Note's running 4.4 that are having problems to find the ROM version/region, installed s/w, combination of s/w, configuration, or settings that are causing it. You guys huddling together to figure it out will be faster than waiting for a fix that may never come.
Click to expand...
Click to collapse
I think the percentage is bigger than we think. I have tried all the floor models at my local best buy and they to mess up. I to doubt samsung will fix this. I am not sure how to isolate the problem. The note pro I have access to is completely stock, the stock wallpapers for lock and home screens have not even been changed. I have factory reset both devices and have not installed any app other than the pre-installed stuff. Calling samsung doesnt help, I have already read of other forum members sending their tablets in to just have them sent back without being "fixed". There are more than one thread about this throughout XDA and other sites.
I have owned my 2014 since nov 2013. I haven't changed anything on it other than the update to 4.4. Thats why I beleive it is the cause. The moment after the update was complete, the chromecast problem happened.
I will say again, chromecast works as always fof many, many apps. Listening to google play music and google play movies seems to be the biggest offenders. I have read that the Crackle app has problems too.
My 2014 and pro are bogh 32g US version purchased straight from samsung. Both have never been rooted.
chgambini said:
I think the percentage is bigger than we think.
Click to expand...
Click to collapse
I very much agree with this - I have tried Costco and BB models - 2014 and Tab Pro and Note Pro - all had the same issue. It's the lucky few that haven't had it.
blinkingled said:
I very much agree with this - I have tried Costco and BB models - 2014 and Tab Pro and Note Pro - all had the same issue. It's the lucky few that haven't had it.
Click to expand...
Click to collapse
I assume your using google play music/movies too
chgambini said:
I assume your using google play music/movies too
Click to expand...
Click to collapse
Pretty much anything that works with Chromecast crashes it. Twit Cast for Chromecast, Google Play Music and Videos, Chrome Beta, YouTube etc.
blinkingled said:
Pretty much anything that works with Chromecast crashes it. Twit Cast for Chromecast, Google Play Music and Videos, Chrome Beta, YouTube etc.
Click to expand...
Click to collapse
I can watch youtube and hbogo with no problems. Do you have the video playback issues as well? If I try to watch a video from g+ or a preview of a movie on google play, I will either get a black screen with audio only, or massive stuttering and lines while watching on the tablet in full screen.
I have sent feed back to Google on the music and movies apps. Lets see what kind of reply we get from them
blinkingled said:
I very much agree with this - I have tried Costco and BB models - 2014 and Tab Pro and Note Pro - all had the same issue. It's the lucky few that haven't had it.
Click to expand...
Click to collapse
What regions does it affect? Obviously you're in the U.S. My working device is from Latin America. Do Chromecast's themselves come with a single version of s/w that's deployed identically worldwide? Google updates Chromecast. Was the Chromecast's firmware the same before and after the N10.1-14 started crashing? You need to figure out what the devices that aren't working have in common and that includes Chromecast itself. Does screen mirroring work by means other than Chromecast? You'd think if something was majorly wrong with the N10.1-14's video, networking, or s/w drivers screen mirroring would be borked consistently. Just some things to think about.
I'll give you an example. Some folks with the OG N10.1 reported importing PDF's crashed S Note. A bunch of us weren't having any issues. We found out that even though the OG 10.1 was only six months old at the time there were eight different versions of S Note installed depending on region. Two of the eight had the PDF problem. Therefore I'd be careful about making assumptions about how wide spread the issue is. Chromecast's pretty popular and I think there would be more "WTF?" posts if it was as widespread as some think it is.
SamsE=BarryH_GEG;52798927]What regions does it affect? Obviously you're in the U.S. My working device is from Latin America. Do Chromecast's themselves come with a single version of s/w that's deployed identically worldwide? Google updates Chromecast. Was the Chromecast's firmware the same before and after the N10.1-14 started crashing? You need to figure out what the devices that aren't working have in common and that includes Chromecast itself. Does screen mirroring work by means other than Chromecast? You'd think if something was majorly wrong with the N10.1-14's video, networking, or s/w drivers screen mirroring would be borked consistently. Just some things to think about.
I'll give you an example. Some folks with the OG N10.1 reported importing PDF's crashed S Note. A bunch of us weren't having any issues. We found out that even though the OG 10.1 was only six months old at the time there were eight different versions of S Note installed depending on region. Two of the eight had the PDF problem. Therefore I'd be careful about making assumptions about how wide spread the issue is. Chromecast's pretty popular and I think there would be more "WTF?" posts if it was as widespread as some think it is.[/QUOTE]
I have 2 chromecast in my house. Yes the are updated OTA directly from google. The firmware was the same before and after the update. My note 3 on 4.4 works perfectly with chromecast with the same version of google play music/movies and the ssme apps overall installed. Samsungs allsharecast will work on my tablets. The only devices I have that exhibit this behavior are the note 2014 and note pro. Both stock us version, both crash on play music/movies, both have random issues with video play back. The 2014 was fine before 4.4, so this leads me to believe the update is causing it. I did not try the pro until I had issues with the 2014 to see if it was the same so I cant say it was good or bad out of the box. The pro did rec an update right before the 2014 rec 4.4.
chgambini said:
I have 2 chromecast in my house. Yes the are updated OTA directly from google. The firmware was the same before and after the update. My note 3 on 4.4 works perfectly with chromecast with the same version of google play music/movies and the ssme apps overall installed. Samsungs allsharecast will work on my tablets. The only devices I have that exhibit this behavior are the note 2014 and note pro. Both stock us version, both crash on play music/movies, both have random issues with video play back. The 2014 was fine before 4.4, so this leads me to believe the update is causing it. I did not try the pro until I had issues with the 2014 to see if it was the same so I cant say it was good or bad out of the box. The pro did rec an update right before the 2014 rec 4.4.
Click to expand...
Click to collapse
Comparing to other devices isn't going to help you. Hell, my N10.1-14 works fine with Chromecast on 4.4 and others have said the same thing. So the issue isn't where it works, it's where it doesn't and why. Out of what you said this is what I took away...
The problem was introduced with 4.4 because your N10.1-14 worked fine with the same Chromecast device on 4.3. Is it something Samsung did in 4.4 specific to the Pros/Notes? Just for U.S. versions? Is it an issue in 4.4 itself that the specific Samsung s/w on the Pro/Notes is aggravating? It's not universal to 4.4 or 4.4 on the Pro/Notes because the problem's not happening beyond a subset of devices.
Your device is from the U.S. as is @blinkingled 's. Where are the other people reporting issues device's from?
You said the problem was there after a complete reset. Does that include preventing Google and Samsung from applying apps and settings stored in your accounts when you first start setup? I'd hard reset again skipping both the Samsung and Google account sign-ins. Go to Accounts in settings and add Google but quickly uncheck all the syncs so they don't add anything to your device. Same thing if Play tries to restore or update your apps. In Play, install one of the apps that was causing crashes. If with nothing but the basics on your tablet Chromecast is still crashing it's something in Samsung's update causing the problem. At least for the U.S.
You mentioned the Pro receiving an update. Since this isn't a universal problem there's no assurance that Samsung's devs even know about it. If 100 people worldwide report a problem and it makes it in to Samsung's problem tracking system that's a blip compared to the millions of devices sold since the N10.1-14 became available in October. And since it's related to third party h/w it goes to the bottom of the line. In the scenario I described above with the OG Tab 10.1 PDF issue Samsung did nothing to specifically address the problem even though people from affected regions reported it. The next wave of planned updates fixed the problem because all regions received an S Note update. So if we can't figure out the issue it's highly unlikely Samsung will either. That means if an update corrects it it'll be coincidence not because Samsung's diligently working on a solution. In other words, people affected that live and die by Chromecast are potentially going to have to live with this for a while.
EDIT: Do you guys with issues have external SD cards? Try removing them and soft resetting the tablet (hold power for seven seconds) to see if that makes a difference.
BarryH_GEG said:
Comparing to other devices isn't going to help you. Hell, my N10.1-14 works fine with Chromecast on 4.4 and others have said the same thing. So the issue isn't where it works, it's where it doesn't and why. Out of what you said this is what I took away...
The problem was introduced with 4.4 because your N10.1-14 worked fine with the same Chromecast device on 4.3. Is it something Samsung did in 4.4 specific to the Pros/Notes? Just for U.S. versions? Is it an issue in 4.4 itself that the specific Samsung s/w on the Pro/Notes is aggravating? It's not universal to 4.4 or 4.4 on the Pro/Notes because the problem's not happening beyond a subset of devices.
Your device is from the U.S. as is @blinkingled 's. Where are the other people reporting issues device's from?
You said the problem was there after a complete reset. Does that include preventing Google and Samsung from applying apps and settings stored in your accounts when you first start setup? I'd hard reset again skipping both the Samsung and Google account sign-ins. Go to Accounts in settings and add Google but quickly uncheck all the syncs so they don't add anything to your device. Same thing if Play tries to restore or update your apps. In Play, install one of the apps that was causing crashes. If with nothing but the basics on your tablet Chromecast is still crashing it's something in Samsung's update causing the problem. At least for the U.S.
You mentioned the Pro receiving an update. Since this isn't a universal problem there's no assurance that Samsung's devs even know about it. If 100 people worldwide report a problem and it makes it in to Samsung's problem tracking system that's a blip compared to the millions of devices sold since the N10.1-14 became available in October. And since it's related to third party h/w it goes to the bottom of the line. In the scenario I described above with the OG Tab 10.1 PDF issue Samsung did nothing to specifically address the problem even though people from affected regions reported it. The next wave of planned updates fixed the problem because all regions received an S Note update. So if we can't figure out the issue it's highly unlikely Samsung will either. That means if an update corrects it it'll be coincidence not because Samsung's diligently working on a solution. In other words, people affected that live and die by Chromecast are potentially going to have to live with this for a while.
EDIT: Do you guys with issues have external SD cards? Try removing them and soft resetting the tablet (hold power for seven seconds) to see if that makes a difference.
Click to expand...
Click to collapse
Yes I have done a hard reset on both devices, skiping past adding any accounts and unchecking the restore app data box.
---------- Post added at 10:57 AM ---------- Previous post was at 10:53 AM ----------
BarryH_GEG said:
Comparing to other devices isn't going to help you. Hell, my N10.1-14 works fine with Chromecast on 4.4 and others have said the same thing. So the issue isn't where it works, it's where it doesn't and why. Out of what you said this is what I took away...
The problem was introduced with 4.4 because your N10.1-14 worked fine with the same Chromecast device on 4.3. Is it something Samsung did in 4.4 specific to the Pros/Notes? Just for U.S. versions? Is it an issue in 4.4 itself that the specific Samsung s/w on the Pro/Notes is aggravating? It's not universal to 4.4 or 4.4 on the Pro/Notes because the problem's not happening beyond a subset of devices.
Your device is from the U.S. as is @blinkingled 's. Where are the other people reporting issues device's from?
You said the problem was there after a complete reset. Does that include preventing Google and Samsung from applying apps and settings stored in your accounts when you first start setup? I'd hard reset again skipping both the Samsung and Google account sign-ins. Go to Accounts in settings and add Google but quickly uncheck all the syncs so they don't add anything to your device. Same thing if Play tries to restore or update your apps. In Play, install one of the apps that was causing crashes. If with nothing but the basics on your tablet Chromecast is still crashing it's something in Samsung's update causing the problem. At least for the U.S.
You mentioned the Pro receiving an update. Since this isn't a universal problem there's no assurance that Samsung's devs even know about it. If 100 people worldwide report a problem and it makes it in to Samsung's problem tracking system that's a blip compared to the millions of devices sold since the N10.1-14 became available in October. And since it's related to third party h/w it goes to the bottom of the line. In the scenario I described above with the OG Tab 10.1 PDF issue Samsung did nothing to specifically address the problem even though people from affected regions reported it. The next wave of planned updates fixed the problem because all regions received an S Note update. So if we can't figure out the issue it's highly unlikely Samsung will either. That means if an update corrects it it'll be coincidence not because Samsung's diligently working on a solution. In other words, people affected that live and die by Chromecast are potentially going to have to live with this for a while.
EDIT: Do you guys with issues have external SD cards? Try removing them and soft resetting the tablet (hold power for seven seconds) to see if that makes a difference.
Click to expand...
Click to collapse
No sdcard. I will try a hard reset again, unchecking all the google sync stuff. Got nothing to lose.......
Try downloading a free show or trailer in Samsung Hub Video. Does the issue occur with a Samsung app using Samsung-sourced content?
BarryH_GEG said:
Try downloading a free show or trailer in Samsung Hub Video. Does the issue occur with a Samsung app using Samsung-sourced content?
Click to expand...
Click to collapse
OK, hard reset, nothing installed, skipped past adding accounts. Went to settings, back up and reset unchecked restore apps data and added my Google account with all sync unchecked. Google music and movie still cause system.ui crash when touching the notification bar. Samsung hub plays fine. Samsung hub does use allsharecast to my Samsung TV and not the chromecast though
chgambini said:
OK, hard reset, nothing installed, skipped past adding accounts. Went to settings, back up and reset unchecked restore apps data aND added my Google account with all sync unchecked. Google music and movie still cause system.ui crash when touching the notification bar. Samsung hub plays fine. Samsung hub does use all casts hare to my Samsung TV and not the chrome cast though
Click to expand...
Click to collapse
Try turning off Chrome in Application Manager.
BarryH_GEG said:
Try turning off Chrome in Application Manager.
Click to expand...
Click to collapse
No change, still crashes
BarryH_GEG said:
The problem was introduced with 4.4 because your N10.1-14 worked fine with the same Chromecast device on 4.3. Is it something Samsung did in 4.4 specific to the Pros/Notes? Just for U.S. versions? Is it an issue in 4.4 itself that the specific Samsung s/w on the Pro/Notes is aggravating? It's not universal to 4.4 or 4.4 on the Pro/Notes because the problem's not happening beyond a subset of devices.
Your device is from the U.S. as is @blinkingled 's. Where are the other people reporting issues device's from?
You said the problem was there after a complete reset. Does that include preventing Google and Samsung from applying apps and settings stored in your accounts when you first start setup? I'd hard reset again skipping both the Samsung and Google account sign-ins. Go to Accounts in settings and add Google but quickly uncheck all the syncs so they don't add anything to your device. Same thing if Play tries to restore or update your apps. In Play, install one of the apps that was causing crashes. If with nothing but the basics on your tablet Chromecast is still crashing it's something in Samsung's update causing the problem. At least for the U.S.
You mentioned the Pro receiving an update. Since this isn't a universal problem there's no assurance that Samsung's devs even know about it. If 100 people worldwide report a problem and it makes it in to Samsung's problem tracking system that's a blip compared to the millions of devices sold since the N10.1-14 became available in October. And since it's related to third party h/w it goes to the bottom of the line. In the scenario I described above with the OG Tab 10.1 PDF issue Samsung did nothing to specifically address the problem even though people from affected regions reported it. The next wave of planned updates fixed the problem because all regions received an S Note update. So if we can't figure out the issue it's highly unlikely Samsung will either. That means if an update corrects it it'll be coincidence not because Samsung's diligently working on a solution. In other words, people affected that live and die by Chromecast are potentially going to have to live with this for a while.
EDIT: Do you guys with issues have external SD cards? Try removing them and soft resetting the tablet (hold power for seven seconds) to see if that makes a difference.
Click to expand...
Click to collapse
That's an extensive and well thought out debugging list - thanks :good: (I had posted a message some time ago to gather info from people having and not having the issue - but I think we only got 2-3 uncertain data points.) But at this point I have tried everything in your post - reset, with and without SD, without restoring apps, with and without updates. It still crashes. And the ChromeCast firmware was last updated was in mid April when it didn't have an issue with 4.3 - so that doesn't seem to be a factor either.
About being in the US - I think OP's tablet is Latin American version if I am not mistaken. It's really a mystery at this point as to why some of them work.
Hi,
My father and I have nexus 4s, I've flashed mine with lollipop from an official image because I couldn't wait for OTA and father got the OTA.
My phone has never really run better while his has recently gotten some huge bug or a virus. The phone can't connect to play services, it can't install apps even from unknown sources, it cannot connect to a PC for data or camera
storage. And the weirdest thing is the fact that after a reboot all notifications and apps in overview stay, so in the overview is filled with like 100+ apps.
The whole thing seems locked down which is really weird, with a lot of experience with ROMs, android, bugs and bricking devices I've never seen anything like this, yet this phone has never been rooted or messed with.
I've managed to backup photos to dropbox because it was installed before the bug and now I've done a factory reset and will be keeping you up on the story.
Any similar situations?
EDIT 1:
It did boot on a 2nd try after like 15min, thats kinda lot of time to build up dalvik istn't it?
I have a new Samsung Galaxy S8 that reboots randomly during the day. The screen will freeze and the phone restarts with no warning. I have heard that it has something to do with the SD card installed, but I have removed my SD card and it continues to reboot. I have also deleted all old apps that are not specifically compatible with Nougat 7.0 thinking about the OS having backward compatibility issues, but the problem persists. Samsung hasn't officially recognized the problem. I had AT&T replace my first S8, but the new replacement reboots more often than the old one. My wife's S8 (bought at the same time) does not have the problem.
UPDATE:
I had AT&T replace my second S8 with S8 number 3. It did not have the rebooting issue until I loaded the first OTA update. Then it started happening again. Following up on the SD card problems that were mentioned, I transferred all of my data from an 8 GB micro SD to a new 32 GB micro SD. The problem seemed to slow down, but it was definitely still there. I booted into Safe Mode and the problem stopped - obviously, the problem was being created by a third party app. Apparently, I missed deleting something in my previous test. I had two different Clock & Weather Apps installed on different pages of my home screen (each set for different locations). I found that one of those Apps that was advertised as a 2017 App was not compatible with 7.0 Nougat. I uninstalled both Apps - that solved the problem. I have since found and installed a Clock & Weather App that was upgraded on May 27, 2017. Everything has been working great since then.
Spiffysprt said:
I have a new Samsung Galaxy S8 that reboots randomly during the day. The screen will freeze and the phone restarts with no warning. I have heard that it has something to do with the SD card installed, but I have removed my SD card and it continues to reboot. I have also deleted all old apps that are not specifically compatible with Nougat 7.0 thinking about the OS having backward compatibility issues, but the problem persists. Samsung hasn't officially recognized the problem. I had AT&T replace my first S8, but the new replacement reboots more often than the old one. My wife's S8 (bought at the same time) does not have the problem.
Click to expand...
Click to collapse
This is not a new issue and has been, recently, reported on all over the place.
Here's a handful of those reports:
Galaxy S8 users are getting plagued by random restarts
The Samsung Galaxy S8 has a random reboot problem and nobody knows why
Samsung Galaxy S8 Random Reboot Issue: Probable Cause And Solutions
Galaxy s8 keeps restarting by itself - Samsung Support Community
Not exactly bootlooping, but random Galaxy S8 reboots should not be a thing
You should be placing this attention to Samsung Support since this, apparently, seems to be a Samsung design flaw.
I wish you the best of luck!
"Live Long and Prosper..."
~Ambassador S'chn T'gai Spock
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
Mine randomly rebooted once when I first got it. I want to say I did something specifically with an app that I normally don't use if i remember right. Needless to say I used it again after that and it has not happened since.
In case it helps. I had the same issue with my s8+. Did a factory restart and it would still restart itself. Mainly when trying to unlock it. So i let it be since i was gone for work. And after about 2 days or so it completely stopped doing that. Its been like 3 weeks and not a single reboot. So maybe it just has to properly install everything or something. I know it shouldnt have done that but it was a new phone with new software so maybe just some glitches somewhere
---------- Post added at 04:30 AM ---------- Previous post was at 04:27 AM ----------
Also incase it is the sd card. Idk if it is but when i restarted it i erased the android and lost.dir folders on my sd card to make sure it didnt have anything on it from my previous phone.
Hi guys,
I had a lot of random reboot yesterday and then I have enabled the option to "forcer l'autorisation d'application sur le stockage externe" (something to give the ability to save apps in the SD card) in the developper options. And since that, I have no more reboot. So just try and let us know if it's working for you too.
Hopefully this will help some with the same issue I had.
A few weeks ago, my Note 4 (SM-N910F, 6.0.1 Touchwiz ROM, rooted, Xposed...) started misbehaving badly, with apps (including system) unexpectedly crashing more and more with time forcing me to reboot regularly.
Factory reset would help, but I had trouble getting the phone exactly like I wanted it, so I kept going back to backups and the instability.
I tried to flash newer ROMs over again and this did not help either.
Another thing that started annoying me at that time was that SPEN input stopped working as text input. I could use the SPEN to draw, in S-Note, or even to swipe or start applications, but as soon as I would try to use handwriting recognition, the keyboard would crash. Direct input was no use either, not crashing but not converting handwriting to text.
I tried to clear cache/data on keyboard, looked around for meaningful SPen applications to clear data on, to no avail.
I did look around the Internet for people with a similar problem but none was really the same and none of the fixes worked for me anyway!
Yesterday, as I was preparing for yet another factory reset and backing up all my apps with Titanium Backup after making a full ROM backup with Flashfire, I noticed TiBu backing up an application I'd not noticed before called Handwriting DB Updater 1.5.0, and decided to give this a try.
As soon as my backups were complete, I went back into TiBu, looked for Handwriting DB Updater 1.5.0, and wiped its data from there. As soon as this was done, handwriting started working again so I decided to delay wiping the phone and I have been able to use it with no crashes for a few hours already.
I believe this is what was making my Note 4 unstable to begin with and I won't need another factory reset, but I'll be monitoring overall stability for the next few days just in case. And hopefully this will help others with handwriting recognition issues as well!
François
The instability infortunately is still there.
But spen keeps working.
Has anyone else noticed that their device certification in the Play Store suddenly shows "Uncertified"? My tablet is totally stock, never tried to root or unlock the bootloader. I just noticed that I couldn't download or update any apps, then suddenly saw this.
Any ideas about what's going on?
Fix
I'm not sure about the "Uncertified" status because I never checked, but I suspect you are having the same issue many other owners have after updating to 7.1.1. I had the problem as well, in which I could not update or download any apps in the Play Store. I would recommend looking at this thread: httpsCOLONSLASHSLASHforums.lenovoDOTcom/t5/Yoga-Book-Android/Lenovo-Yoga-Book-Android-Nougat-Breaks-Google-Play-App-Store/m-p/3834779#M466. (Replace the capitalized words with the corresponding symbols because I'm too new to post external links. The solution it lists about disabling adminstrators and removing VPN's and then restarting did not work for me initially. I ended up doing a factory reset, which solved the problem for a short time. Once it came back the solution from the thread fixed it and I haven't had an issue since.
It's absolutely sickening! Since weeks Google Services stuck on my both devices (X90F and X90L) I tried all the suggestions (factory reset and so on ...) given at this thread:
https://forums.lenovo.com/t5/Yoga-B...aks-Google-Play-App-Store/td-p/3813570/page/3
Nothing works permanently and now, suddenly Play Store says: "Device not certified" . Both devices are not rooted and System-Build is LenovoYB1-X90L_100081_171013 / LenovoYB1-X90F_100083_171013
Turning on battery saver seems to be a viable workaround.
discomega said:
Turning on battery saver seems to be a viable workaround.
Click to expand...
Click to collapse
Not really
Btw I registered the uncertified devices now at https://www.google.com/android/uncertified/. But nothing changed in a positive way. On X90F sometimes over night play store runs and apps were updated. With X90F I always I have to stop play services and play store, delete cache and play store data. Then, after restart apps were updated too.
On both devices are running the identical apps and on my old Nexus7 (LineageOS Android 7.1.2) with same apps, activated builtin administrators and AdGuard-VPN all works flawlessly :good:
I think Lenovo urgently needs to deliver an update to get the devices recertified and pass the Android compatibility test.
Encountered the same. Is there still no fix or update from Lenovo for that?