Related
My phone is a LG G3 T-Mobile, running on 5.0.1 LP OTA updates.
After setting up my zenwatch2 with my phone, the watch pop up the
"Get google play services Android Wear won't run without Google Play services, which are missing from your phone“
On my phone I am running Android Wear ver. 1.3.0.2369832
Google play services ver. 8.3.00
I have done multiple factory reset on the watch but still pop up after synchronising with my phone.
What could be the issue? Watch seems to work fine. Text and notifications shows up fine.
Try to restart the google play services on phone
I've disable it on the phone then it said it will revert to old version. But it didn't. No option under google play for uninstall update. Its greyed out. Once I disable on the phone, well I tried, I reboot and then factory reset zenwatch. Then repeat the entire pairing process all over again. Still nothing. So, I don't know.
When i started the first time, and after I FDR'd I got the message. It went away quickly though.
Nsx93 said:
"Get google play services Android Wear won't run without Google Play services, which are missing from your phone“
Click to expand...
Click to collapse
I've had this message on my SWR50, too, when BT connection to the phone (Edge+) got lost. Android Wear app on phone showed a "connecting" message, while the watch was complaining about missing services. I've rebooted both phone and watch, now it's fine. Hope this does not happen again with the ZW2, which will arrive in 14 days.
I tried everything. It still pop up once in awhile. I am running Blisspop ROM for my lg g3 T-Mobile. Everything is up to date. So, I don't know. Both watch and phone running on lp 5.1.1 ... So, j can't see the conflict there. Both play services updated to current version.
I've had it show up briefly once or twice, but it quickly goes away. Seems like just a minor bug.
Nsx93 said:
My phone is a LG G3 T-Mobile, running on 5.0.1 LP OTA updates.
After setting up my zenwatch2 with my phone, the watch pop up the
"Get google play services Android Wear won't run without Google Play services, which are missing from your phone“
On my phone I am running Android Wear ver. 1.3.0.2369832
Google play services ver. 8.3.00
I have done multiple factory reset on the watch but still pop up after synchronising with my phone.
What could be the issue? Watch seems to work fine. Text and notifications shows up fine.
Click to expand...
Click to collapse
You need Google search to fix the problem.. Make sure Google search is not disable. Clear the cache on Google search in app settings. Then don't open Google search. Because that will be a battery drain.
Sent from my ASUS_Z00A using Xparent BlueTapatalk 2
blazinandroid1 said:
You need Google search to fix the problem.. Make sure Google search is not disable. Clear the cache on Google search in app settings. Then don't open Google search. Because that will be a battery drain.
Sent from my ASUS_Z00A using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Thanks.
I've updated all the gapps. So far it hasn't pop up on the watch, yet!
Been working fine lately.
It would been nice if the connection range is further. Seem pretty short distance, then it will get disconnected.
Nsx93 said:
Thanks.
I've updated all the gapps. So far it hasn't pop up on the watch, yet!
Been working fine lately.
It would been nice if the connection range is further. Seem pretty short distance, then it will get disconnected.
Click to expand...
Click to collapse
Waiting on the source code. So I can start fxing some of those problems.
Sent from my ASUS_Z00A using Xparent BlueTapatalk 2
It would make this watch 10x better if the issues get hammered out.
Look forward to your work.
This is happening on Moto 360 (1st gen) too. Been using the watch fine on my Moto X '13, then today factory reset it paired it with my new phone (moto x pure) and it works fine for a bit, then this notification comes on my watch screen and the watch disconnects. All play services and such are up to date
Every time I factory reset it and re pair it with android wear it will appear once or twice then disappears
It is normal across all Android wear devices. Android Wear requires that Google Search is installed and enabled (not disabled, lol). I have a tendency to disable this feature when I am going through disabling apps on a fresh boot. Just make sure Google Now is able to launch. You don't have to accept to use Google Now, but you should be able to swipe up on home to launch search.
player911 said:
It is normal across all Android wear devices. Android Wear requires that Google Search is installed and enabled (not disabled, lol). I have a tendency to disable this feature when I am going through disabling apps on a fresh boot. Just make sure Google Now is able to launch. You don't have to accept to use Google Now, but you should be able to swipe up on home to launch search.
Click to expand...
Click to collapse
The real reason for that to pop up. Is when the device gets disconnected from the phone. And you are right about Google search.
Anyone got this yet
Sent from my Nexus 6P using XDA-Developers Legacy app
yea just got it. already had assistant but downloaded the updates anyway.
Anyway to force it
Just got a launcher update. But assistant not enabled yet.
Sent from my Nexus 6P using Tapatalk
Does it works with 7.1.1 ?
Sent from my Nexus 6P using XDA-Developers Legacy app
m.t.2012 said:
Does it works with 7.1.1 ?
Click to expand...
Click to collapse
According to this:
https://www.xda-developers.com/google-assistant-now-available-for-all-android-6-0-devices/
Yes, but not worldwide yet...
I just tried updating my play services from 10.2.98 to the newest non beta on apkmirror which is 10.2.99 but assistant is not enabled. I then tried the latest beta which is 10.5.37 but still no assistant. I just got the Google app update to 6.13.x earlier via play store so I figured all I needed was play services but apparently not unless root is causing an issue.
jrg67 said:
I just tried updating my play services from 10.2.98 to the newest non beta on apkmirror which is 10.2.99 but assistant is not enabled. I then tried the latest beta which is 10.5.37 but still no assistant. I just got the Google app update to 6.13.x earlier via play store so I figured all I needed was play services but apparently not unless root is causing an issue.
Click to expand...
Click to collapse
I'm not rooted and updated play services and the Google app and also still have no assistant. So, apparently it is a server side switch that we all just need to wait for. Of course I still don't have the dual tab google app layout, so I'm not holding my breath.
Empty Hand said:
I'm not rooted and updated play services and the Google app and also still have no assistant. So, apparently it is a server side switch that we all just need to wait for. Of course I still don't have the dual tab google app layout, so I'm not holding my breath.
Click to expand...
Click to collapse
That dual tab Google app layout is still a thing? I never got it either and just assumed it was pulled. So for assistant, the Google blog says it's a play services update, naturally that means something else like a server side update too. Silly Google, tricks are for kids.
I have a 6P and 5x both on 7.1.2 beta, no Google Assistant. I have a hunch that apart from having to have the new Google Play Services, that individual accounts have to have the switch thrown on it by Google. Like many of Google's software updates this is liable to take weeks for everyone to see.
I have a 6P, 5X and a 5. Yesterday in an effort to solve another problem, I had clean installed factory 6.0, 7.0, 7.1.1 and 7.1.2(beta) with locked bootloaders and completely stock onto my 6P. None of the phones and none of the factory ROMs had Google Assistant enabled even after updating all stock apps. WTF, Google, after your big announcement that it was available? Aside from the one person in this thread, I haven't heard of anyone having this enabled, even read through over 400 comments in Android Police thread.
Still have not received it. Running stock 7.1.1.
Sent from my Nexus 6P using Tapatalk
It's a server side switch, so we all have to just wait until google flips the switch.
Here's how I did it:
I enrolled with ALL the permissions with the Google (Google Now) app; i.e., News and weather updates.
Then, I downloaded and enrolled with Google Allo. I gave it ALL of the permissions it requested of me. Then I made a few queries with Allo's Google Assistant bot.
It's important that you turn Location and Search histories ON.
I was greeted by Google Assistant shortly thereafter...
Hope this helps!
Janerd said:
It's a server side switch, so we all have to just wait until google flips the switch.
Click to expand...
Click to collapse
honestly it is just matter of adding a single line to build.prob
Code:
ro.opa.eligible_device=true
I know there are all kinds of mods and stuff for rooted/unlocked phones to get Google Assistant, but the official rollout happened recently to a lot of devices. Was the Z one of them? I updated Play Services and the Google app to the latest release version, and tried being in the beta for both of them, and still don't have the assistant. Has anyone got the assistant working on the Z the official way? I'd rather keep stock for Safety Net reasons.
Check your device, i got up this morning with google assistant on my moto z (verizon)
Nope, I still have Now On Tap. Would you mind looking at what version of Play Services and the Google app you have?
Still waiting on assistant too but I'm UK based here but God I swear I'm addicted to updates
Wingdom said:
Nope, I still have Now On Tap. Would you mind looking at what version of Play Services and the Google app you have?
Click to expand...
Click to collapse
Try clearing data?
lollyjay said:
Try clearing data?
Click to expand...
Click to collapse
I just tried it again, along with uninstalling all updates and reinstalling them. No such luck. Maybe they're still working on the rollout...
Wingdom said:
Nope, I still have Now On Tap. Would you mind looking at what version of Play Services and the Google app you have?
Click to expand...
Click to collapse
My version is 10.2.98
I did not see any update on the google play services these two days.
But got up with google assistant ready.
So i guess evil google did it by itself.
I did notice a fast battery drain by google services last night.
---------- Post added at 10:43 PM ---------- Previous post was at 10:39 PM ----------
I have another S7 edge, but has not got any Google assistant.
I guess you need to be patient.
I have owned many nexus devices before, and i did notice there is a delay for devices made at different time.
metrocar said:
I guess you need to be patient.
I have owned many nexus devices before, and i did notice there is a delay for devices made at different time.
Click to expand...
Click to collapse
Thanks for the answer, it's just not what I wanted to hear, lol. Might just get over it and root...
Just got Google assistant on my Moto Z this morning set phone this is probably due to Google enabling the UK service
PL4C3B0 said:
Just got Google assistant on my Moto Z this morning set phone this is probably due to Google enabling the UK service
Click to expand...
Click to collapse
Did you do anything to get it or did it just appear? I am UK and using unlocked from John Lewis on 3 network.
Turned off on tap set installed Google play services 10.2.99 and got nothing but this morning updated Google (beta) and when I long pressed the home button it was ready
PL4C3B0 said:
Turned off on tap set installed Google play services 10.2.99 and got nothing but this morning updated Google (beta) and when I long pressed the home button it was ready
Click to expand...
Click to collapse
I am already on GPS beta. tried turning on tap off/on but still nothing.
This is the beta that I have
PL4C3B0 said:
This is the beta that I have
Click to expand...
Click to collapse
Also set languages as US English
Hi Google!!
I woke up this morning to my new Assistant! No beta anything, just the latest release version of all the apps.
Did all that and nothing then it showed up a couple of hours later. Guessing it must be related. Thanks for the help.
Sent from my XT1650 using XDA Free mobile app
Just thought I'd let people know that I'm in the UK and got Google Assistant working using the following guide:
http://www.xiaomitoday.com/get-google-assistant-on-marshmallow/
I changed the language back to English (UK) after and all seems to be working fine.
On a side note, you need to disable Moto Voice to allow "OK Google" to work.
HTH
Ooms
---------- Post added at 03:45 PM ---------- Previous post was at 03:35 PM ----------
Ok. Just checked again and Google Assistant got disabled. Changed the language to English (US), cleared data and tried again. Seemed to work. Had to do a hybrid language selection with English (US) system language and changed language in input settings to English (UK). It looks like that seems to work.
Just received Google Assistant, pretty useful.
Sent from my XT1650-03 using XDA-Developers Legacy app
I wonder if Moto plans to issue any kind of update to make Moto Voice work with Google Assistant. If you have Moto Voice enabled, you get the old Google Now but the new Google Assistant doesn't work if the screen is locked.
Hello guys.
Many users, including me, stumbled across this problem the past couple of days.
There seems to be an issue with the latest Google Play Store version, which becomes stuck on waiting for network if you try to download something at random times.
This is very frustrating but I found a fix, although temporary until Google updates the play store.
WARNING: This requires root. Also I am not responsible for any damage that happens to your phone, proceed at your own risk as always.
Without further ado, this is what this fix is about:
Go to apps, press the three dot menu on the top right, show system apps, and find Google Play Store.
Once in Google Play Store, press remove updates, or disable and enable the app again, both ways work.
If you see in the notification bar that Google Play Store is updating, CANCEL IT.
Now, this is where is gets interesting.
Normally the Google Play Store will update itself, but we want to stop that until a later date where a fix is pushed out.
Download the app called MyAndroidTools.
Open the app and select the service menu, press system.
Scroll down to Google Play Store.
Find a switch named SelfUpadteChecker and turn it off.
Voila, your play store will now be working properly.
REMINDER: This is not a permanent solution, remember to check again if the play store is fixed at a later date to enable the switch again and update to the latest version.
Have a nice day all.
EDIT 3/4/17 : I found out that these switches may further help stop Google Play store from updating.
Again use at your own risk.
AsldListener
MaintainanceWindowJobService
RescheduleUsingAlarmManager$CheckWifiAndAutoUpdate
RescheduleIUsingBroadcast$AutoUpdateRecheckFrorBroadcast
RescheduleUsingJobScheduler$CheckPreconditionsAndAutoUpdateJobService
SeflUpdateCheckerScheduler$SelfUpdateCheckerTaskService
EDIT 5/4/17, second way.:
I still recommend the first way because it seems the issue is still not resolved, but this may appeal to users who want something less intrusive or don't have root.
I found out that the issue is not yet resolved with the latest google play version, but I was able to make play store work again with the following :
Cleared data of Download Manager with Titanium Backup.
Clered data of Google play services with Titanium Backup.
Rebooted.
I have no idea if this will last, but I was able to download apps after this, without touching the latest verion of Google Play Store.
If you wanna be extra safe uninstall updates from play store as well, but this worked for me without doing so.
Update: 7/4/17:
Zte announced a new software update, namely B02, which should fix this issue without any user actions required.
Thanks @Choose an username... for reminding me.
Hope it works.
Thanks!
What I did was to download an earlier version of the Play Store, install and before running it for the first time, I disabled the SelfUpadteChecker.
But for some reason, the Play store still tried to download the update, it just crashed after the download. The funny thing is, during the 5 seconds between starting Play Store and the crash, I was able to download an app update.
Which version of Play Store should I use?
Just to clarify, I use the Chinese firmware, so I cannot remove updates, it is not a system app. I can only uninstall it completely.
.
Thanks man. It is working on me right now.
Glad it does.
If it helped hit that thanks button.
I'll update it soon with some further findings as well.
WesTD said:
Thanks man. It is working on me right now.
Click to expand...
Click to collapse
Were you able to unbrick your Axon 7? I read it was in DFU mode wasn't it ?
jimbo77 said:
Were you able to unbrick your Axon 7? I read it was in DFU mode wasn't it ?
Click to expand...
Click to collapse
unbrick one is my friend's. it is cn version, mine is good.
It doesn't require a root. Just cancel updating after you uninstall updates and you are good for some time at least.
On mine, it seems to use the Download Manager app for ALL downloads, including the Play store. If you go to the settings in Download Manager, you'll see a "Download files only via Wi-Fi. Untick that box and Play Store starts working properly again.
I can only assume that the crappy Download Manager is intercepting and controlling all download requests.
mitchelln said:
On mine, it seems to use the Download Manager app for ALL downloads, including the Play store. If you go to the settings in Download Manager, you'll see a "Download files only via Wi-Fi. Untick that box and Play Store starts working properly again.
I can only assume that the crappy Download Manager is intercepting and controlling all download requests.
Click to expand...
Click to collapse
Mine's unticked and still happens.
First post updated.
Is this not the cause? https://support.google.com/googlepl...89771776-1522920403&p=uncertified_device&rd=1
Sent from my ZTE A2017U using Tapatalk
Narada2XK said:
Is this not the cause? https://support.google.com/googlepl...89771776-1522920403&p=uncertified_device&rd=1
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I doubt it, it can't work on a supposedly uncertified device and all of a sudden stop working.
Or the device showing up as certified and all of a sudden becomes uncertified.
I personally think a play store update is broken most likely, because it has been reported from rooted and stock users, plus on other devices rather than the Axon 7 as well.
Guide updated.
@nfsmw_gr You should prolly write down somewhere in the OP (preferrably big, and where it says that it is not a permanent solution) that ZTE announced an upcoming B02 with fixes including this one.
It shouldn't be too far away since it has already rolled out to Chinese versions.
thanks for the fix though
Choose an username... said:
@nfsmw_gr You should prolly write down somewhere in the OP (preferrably big, and where it says that it is not a permanent solution) that ZTE announced an upcoming B02 with fixes including this one.
It shouldn't be too far away since it has already rolled out to Chinese versions.
thanks for the fix though
Click to expand...
Click to collapse
Gotcha, will do.
Is there any other info about this upcoming update? Link?
GuitarJozz said:
Is there any other info about this upcoming update? Link?
Click to expand...
Click to collapse
Check out this thread:
https://forum.xda-developers.com/axon-7/how-to/bugfix-raw-appdrawer-update-a2017g-t3585515
Note that I only have one Google account on the device
I bought a brand new sealed Samsung Galaxy Tab S3. I setup the device for the first time and went straight to updating to Marshmallow which then allowed me to finally update to Oreo. So then I tried to install an app that I already paid for. But it said I didn't pay for it (says $3.99 instead of INSTALL). So I thought that maybe it's from a fishy developer who makes their apps temporary free (P.AG.F.) and pulled the rug from under me. But then I noticed all of my paid apps are UNPAID. So then I decided to go for a legit developer who I was confident is a good developer (Nova Launcher Prime), and even on the Play Store page it said I have to pay money for it even though I already purchased it on my Google account. Even when I click on "Purchased Apps" the apps show as purchased, but as soon as I go to the app's page, it show as unpaid.
So I decided to maybe factory reset the device. Nope. The problem persisted. I checked for an OS update past Android 8.0.0. There was no update. So then I decided to lookup an APK mirror for Google Play Services (using Play Services Info), and I downloaded the correct app for my device (architecture and dpi). I installed the latest Play Services. But in Play Services info it shows that my newly installed App is still the old version from 2016. On Play Services Info it says I need to install the 2018 version (obviously I tried to). It didn't do anything. Still did not work
I am wondering if I got a botched update of Oreo. What do I do? I am out ideas at this point. Man what the heck???
EDIT: Play Services version 12.6.88 (also the updated OS install this version)
poetryrocksalot said:
I bought a brand new sealed Samsung Galaxy Tab S3. I setup the device for the first time and went straight to updating to Marshmallow which then allowed me to finally update to Oreo. So then I tried to install an app that I already paid for. But it said I didn't pay for it (says $3.99 instead of INSTALL). So I thought that maybe it's from a fishy developer who makes their apps temporary free (P.AG.F.) and pulled the rug from under me. But then I noticed all of my paid apps are UNPAID. So then I decided to go for a legit developer who I was confident is a good developer (Nova Launcher Prime), and even on the Play Store page it said I have to pay money for it even though I already purchased it on my Google account. Even when I click on "Purchased Apps" the apps show as purchased, but as soon as I go to the app's page, it show as unpaid.
So I decided to maybe factory reset the device. Nope. The problem persisted. I checked for an OS update past Android 8.0.0. There was no update. So then I decided to lookup an APK mirror for Google Play Services (using Play Services Info), and I downloaded the correct app for my device (architecture and dpi). I installed the Play Services. But in Play Services info it shows that my newly installed App is still the old version from 2016. On Play Services Info it says I need to install the 2018 version (obviously I tried to). It didn't do anything.
I am wondering if I got a botched update of Oreo. What do I do? I am out ideas at this point. Man what the heck???
Click to expand...
Click to collapse
I'm sure it's not the device. Check to make sure you have the latest version of play store. You can do that using the three bar menu in play store and going to settings.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'm sure it's not the device. Check to make sure you have the latest version of play store. You can do that using the three bar menu in play store and going to settings.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Play store is up to date. Play services is also up to date. I can't even downgrade play services to a version below 12.6.88.
[This post is edited]
poetryrocksalot said:
Play store is up to date. Play services is also up to date. I can't even downgrade play services to a version below 12.6.88.
[This post is edited]
Click to expand...
Click to collapse
That's interesting. Mine is 10.2.06 and says it's up to date. It's also working fine. Did your device update to Oreo on it's own or did you flash it with Odin? You're in the US, right?
Edit, my play services is 12.2.85. Play store is 10.2.06
Sent from my [device_name] using XDA-Developers Legacy app
Also, make sure you are not in your "Secure Folder" when running play store. It will not access your account properly and will force you to pay for everything again.
Can you access Play store from a computer? Do you still see the apps you paid for?
Otherwise, I'd contact Google Support and see what is wrong with your account.
jd1639 said:
That's interesting. Mine is 10.2.06 and says it's up to date. It's also working fine. Did your device update to Oreo on it's own or did you flash it with Odin? You're in the US, right?
Edit, my play services is 12.2.85. Play store is 10.2.06
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Oh man what the heck. What do I do? My device won't let me downgrade. Oh man. I am screwed. Edit: Yes everything is fine on all of my devices. Including Android emulators. I turned on the "use secure folder" during factory setup. But when I click on Secure Folder it tells me I need to sign in to my Samsung account in order to use it. So I am not even sure if Secure Folder is the issue. Cause it wont even let me into the app unless I sign up. Play Services is 12.6.8 no downgrade allowed. Play Store is 10.2.06 ???
poetryrocksalot said:
Oh man what the heck. What do I do? My device won't let me downgrade. Oh man. I am screwed.
Click to expand...
Click to collapse
You're not screwed. How did you get Oreo on your device? There isn't a US version so I'm assuming you used Odin. If so did you use the UK version. You're right, you won't be able to down grade to nugat but I'm on Oreo, in the US, and it's working fine.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
You're not screwed. How did you get Oreo on your device? There isn't a US version so I'm assuming you used Odin. If so did you use the UK version. You're right, you won't be able to down grade to nugat but I'm on Oreo, in the US, and it's working fine.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Nope. I read news today that Samsung Tab S3 in the US are rolling out Oreo updates. I got excited and I was like oh what a coincidence because that day was the same day I decided to open up my brand new Samsung Galaxy Tab S3 from the sealed retail packaging. So like I really didn't do much. No tweaks. No strange configuration or app installations. I literally went through Android settings and installed the updates through the official "search for update" method. Note that the update service found the Marshmallow update and forced me to install it before I would be able to find the Oreo update.
No Odin. No flashing. No rooting. No Adb. Nothing nada. EDIT: It's possible I bought a NON-US version of Tab S3, but I don't see how that is relevant because that version of Tab S3 should have Play Store bugs ironed out by now.
poetryrocksalot said:
Nope. I read news today that Samsung Tab S3 in the US are rolling out Oreo updates. I got excited and I was like oh what a coincidence because that day was the same day I decided to open up my brand new Samsung Galaxy Tab S3 from the sealed retail packaging. So like I really didn't do much. No tweaks. No strange configuration or app installations. I literally went through Android settings and installed the updates through the official "search for update" method. Note that the update service found the Marshmallow update and forced me to install it before I would be able to find the Oreo update.
No Odin. No flashing. No rooting. No Adb. Nothing nada. EDIT: It's possible I bought a NON-US version of Tab S3, but I don't see how that is relevant because that version of Tab S3 should have Play Store bugs ironed out by now.
Click to expand...
Click to collapse
The US version of Oreo isn't available for Odin flash yet, otherwise I'd give it a try and see if it's an issue with the firmware. But I don't think even Samsung would have messed up play store. If it was just released it may be available later today.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
The US version of Oreo isn't available for Odin flash yet, otherwise I'd give it a try and see if it's an issue with the firmware. But I don't think even Samsung would have messed up play store. If it was just released it may be available later today.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I feel like if I flashed an Oreo ROM then the problem would disappear. Is there no one else from the US beside me who has updated through the official outlet?
On my Oreo Play Services is v12.6.85 and Play store is v10.2.06-all and I see my paid for apps without issues.
aspexil said:
On my Oreo Play Services is v12.6.85 and Play store is v10.2.06-all and I see my paid for apps without issues.
Click to expand...
Click to collapse
Man. Wtf why does this always happen to me with Google? Like in YouTube, my old playlists show up on my PC Chrome Browser. But they don't even exist in the YouTube app (only the new playlists appear). And on YouTube, there is exactly ONE youtuber that I can't toggle notification for, and that is Marquez Brownlee. But if I made another YouTube account I can toggle on the notification (the ringing bell symbol) for this YouTuber just fine.
NOBODY has these issue except me. Why?
I HAVE INCLUDED SCREENSHOTS AND PICTURES. SOMEBODY HELP ME
jd1639 said:
You're not screwed. How did you get Oreo on your device? There isn't a US version so I'm assuming you used Odin. If so did you use the UK version. You're right, you won't be able to down grade to nugat but I'm on Oreo, in the US, and it's working fine.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Oh I meant that I can't downgrade Play Services, as in I can't install an older version of Play Services.
Another Picture shows the Play Store works fine on other devices. Also here is video of Marquez Brownlee notification problem if you don't believe me. Problem has existed for years already and still hasn't been fixed.
Edit: Second video is portrait because I'm taking it with the Tab S3 with a heavy armored Gumdrop case and can't hold it in landscape (small hand and body) while using the mouse. Don't have tripod either and I was trying to obscure private information.
It isn't that we don't believe you. We do. But there is something wrong with your Google account. If it was me I would factory reset the device and go through the re-install of the Google Account. Somehow Android is not getting updated with your Google Account info so either it is a connectivity issue with Google or something with the install process.
aspexil said:
Also, make sure you are not in your "Secure Folder" when running play store. It will not access your account properly and will force you to pay for everything again.
Can you access Play store from a computer? Do you still see the apps you paid for?
Otherwise, I'd contact Google Support and see what is wrong with your account.
Click to expand...
Click to collapse
SOLVED.
You have to turn off that option during initial "factory" setup. I couldn't turn it off because I didn't have or don't remember my Samsung Account. You need the Samsung Account in order to go past the login screen for "Secure Folder". As far as I know, there is no way to turn off secure folder after it is turned on without a Samsung Account. Deactivating/disabling the Secure Folder app also did not work. I fixed it by factory resetting the device and making sure that the initial toggle for Secure Folder is set to "OFF" (I think the reset is a necessary prerequisite). It looks like the issue is poor software design. Being required to have an account to turn if off, while being able to turn it on without the account is just a terrible choice in design. User aspexil, you have been thanked.
This post has been edited.
poetryrocksalot said:
SOLVED.
You have to turn off that option during initial "factory" setup. I couldn't turn it off because I didn't have or don't remember my Samsung Account. You need the Samsung Account in order to go past the login screen for "Secure Folder". As far as I know, there is no way to turn off secure folder after it is turned on without a Samsung Account. Deactivating the Secure Folder app also did not work. It looks like the issue is poor software design.
Click to expand...
Click to collapse
Glad you got it solved. That might be something new with Oreo. I didn't have that problem when I first got my tab. Ever since it's been rooted and I've never had a Samsung account. Or maybe I turned it off when initially setting up the tab.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Glad you got it solved. That might be something new with Oreo. I didn't have that problem when I first got my tab. Ever since it's been rooted and I've never had a Samsung account. Or maybe I turned it off when initially setting up the tab.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
UNSOLVED.
Actually it's unsolved again. I typed down Nova Launcher in the search box to check if I have it "paid". And it showed up as paid. But now I realized that I was looking for Nova Launcher Prime. Damn it. I guess I need to flash my Tab S3 to a reliable ROM then?
poetryrocksalot said:
UNSOLVED.
Actually it's unsolved again. I typed down Nova Launcher in the search box to check if I have it "paid". And it showed up as paid. But now I realized that I was looking for Nova Launcher Prime. Damn it. I guess I need to flash my Tab S3 to a reliable ROM then?
Click to expand...
Click to collapse
When you factory reset did it reset to Android v7.1? Maybe just stop there and see if you can get the tablet to work before applying Android v8.0? I haven't used anything but stock so don't know what ROM to use.
aspexil said:
When you factory reset did it reset to Android v7.1? Maybe just stop there and see if you can get the tablet to work before applying Android v8.0? I haven't used anything but stock so don't know what ROM to use.
Click to expand...
Click to collapse
Nope. When I factory reset. It reset to Android Oreo 8.0.0. Play Services installed was 12.6.85 (instead of 12.6.88, I think I actually installed 12.6.88 manually via sideloading). The play store version is the same 10.2.06.
So I am wondering which ROM provided online is legitimately unchanged and STOCK so I can just flash via Odin. Then install the Oreo update via WiFi (I am assuming I received a corrupted update that won't happen again).
Also, one guy told me from another thread that he had the same issue and said he just waited a few days and let Play Services "sync" and it just fixed itself automatically. Although, I don't know if he really does have the same problem.
poetryrocksalot said:
Nope. When I factory reset. It reset to Android Oreo 8.0.0. Play Services installed was 12.6.85 (instead of 12.6.88, I think I actually installed 12.6.88 manually via sideloading). The play store version is the same 10.2.06.
So I am wondering which ROM provided online is legitimately unchanged and STOCK so I can just flash via Odin. Then install the Oreo update via WiFi (I am assuming I received a corrupted update that won't happen again).
Also, one guy told me from another thread that he had the same issue and said he just waited a few days and let Play Services "sync" and it just fixed itself automatically. Although, I don't know if he really does have the same problem.
Click to expand...
Click to collapse
I'm pretty sure you will not be able to install nougut firmware after installing Oreo. The bootloader for Oreo is new and Samsung usually trips an e-fuse when updating the bootloader. But you can give it a try and then letting the device update. I get firmware from updato. But be advised that Oreo for the us isn't available yet (nougut is there). The UK version works fine, though. That's what I'm on.
PS, you'll have to enable developer options and then oem unlock to use Odin.
Sent from my [device_name] using XDA-Developers Legacy app