Related
I did a search and I haven't found any info online. Within the past month or so, I have been getting google services connectivity issues where the colors on the bars switch on and off from white to green (meaning there is internet connectivity but no connection to google services). I don't get this problem when I am connected directly to wifi.
This is annoying because if I sign on gchat/gmail, there is a delay until I receive the updated information.
I was hoping that 2.3.4 would resolve this issue, but it still remains.
There is a thread going on about this issue where other people have reported seeing this:
http://www.google.com/support/forum...ad?fid=7c7a962fd3ae87e20004a26b2f3f005b&hl=en
Has anyone on the forums experienced this issue? Are there problems with the google services currently? Thanks in advance.
this also happens the other way around. i'm not connected to a phone service, but can see a signal, and when wifi is active and connected, the green signal bars turn green, even though 'no service' is displayed in the notifications.
I've noticed the same thing. Its been happening for the last few weeks.
Sent from my Nexus S using XDA Premium App
I have experienced problems with the Google location services on 3G. Since I have gotten the Nexus S and am on 3G my location is always "temporarily not available" - 2.3.3, 2.3.4, various versions of Maps - no fix. Tried clearing out the data and cache in Google services framework, Maps - no go - still same problem.
WiFi and GPS are fine. Tomorrow I will go to service center and see if it is some how related to the phone or the carrier network..
Gmail and Talk seem to work ok....
I have the same problem, connection to google is lost when the phone sleeps and sometimes randomly. I have looked everywhere but can't find any fix or official response. This started around April 14.
This issue is so frustrating, it carries over from rom to rom, my phone is basically useless now!
I had to switch to regular voicemail, cause Google voice is so delayed, gmail and google talk are basically useless too.
Sent from my Nexus S using XDA Premium App
I am running Netflix version 3.9.1 build 4105 and Android 4.4.2.
When I open Netflix the program just sits and spins and spins then gives me a "Sorry we could not reach Netflix Service. Please try again later (-9)". Then I clear app data and after I do that and relaunch then I get the extremely common 15001 error (that is impossible to actually troubleshoot..).
I have read multiple people having issues with Netflix, but that was when they released a patch that broke it and I am pretty sure that isn't a common problem anymore. I have one of the apps that show network activity and all I get is random hits of like 20-30 KB/s max while trying to launch Netflix. I have tried this on two completely different networks, so I don't think it has anything to do with my network.
My device is rooted with TWRP installed, but I don't see how this could have any affect on Netflix (it never did on my old rooted Nexus 7 running Cyanogen Mod).
Is there something I can try that maybe I haven't heard yet? I even tried clearing the Google Services Framework cache/data (as this helped people in the past) and that changed nothing above. Not being able to use Netflix is a huge problem for me and I am hoping someone has run into this on our devices. I imagine Netflix is one of the most common Apps used.
Thanks for any help or ideas anyone can provide. If I need to I'll restore the tablet with Fastboot, but there is no guarantee that will work and an obvious pain if it doesn't.
Edit: Read the latest comments on Netflix and it seems there are still plenty of people having problems just like mine. I guess I may be waiting for a new version to release??
NCSUZoSo said:
I am running Netflix version 3.9.1 build 4105 and Android 4.4.2.
When I open Netflix the program just sits and spins and spins then gives me a "Sorry we could not reach Netflix Service. Please try again later (-9)". Then I clear app data and after I do that and relaunch then I get the extremely common 15001 error (that is impossible to actually troubleshoot..).
I have read multiple people having issues with Netflix, but that was when they released a patch that broke it and I am pretty sure that isn't a common problem anymore. I have one of the apps that show network activity and all I get is random hits of like 20-30 KB/s max while trying to launch Netflix. I have tried this on two completely different networks, so I don't think it has anything to do with my network.
My device is rooted with TWRP installed, but I don't see how this could have any affect on Netflix (it never did on my old rooted Nexus 7 running Cyanogen Mod).
Is there something I can try that maybe I haven't heard yet? I even tried clearing the Google Services Framework cache/data (as this helped people in the past) and that changed nothing above. Not being able to use Netflix is a huge problem for me and I am hoping someone has run into this on our devices. I imagine Netflix is one of the most common Apps used.
Thanks for any help or ideas anyone can provide. If I need to I'll restore the tablet with Fastboot, but there is no guarantee that will work and an obvious pain if it doesn't.
Edit: Read the latest comments on Netflix and it seems there are still plenty of people having problems just like mine. I guess I may be waiting for a new version to release??
Click to expand...
Click to collapse
I have the exact same problem! No matter what it's the same error, restoring the tablet doesn't work either.
Screw Netflix, use TV portal! https://drive.google.com/file/d/0BzI_9bXSPgLUX0kwVV8wd3lsTGM/view
When you grab a movie with TV portal, then use Tubemate to download mp4 quality movies of your choice. (touch the green arrow above to get the download interface)
http://www.androidfreeware.net/download-youtube-tubemate.html
I don't think anyone has problems these days ripping off movies, however streaming thousands of movies and TV shows is more convenient by a mile (especially on a tablet).
That is indeed one reason Google & apple push to get rid of the power of personal storage and force the cloud.
When Netflix won't work when you finally settle for a movie, it's nice to have options.
The measly amount Netflix charges is worth it, they have a good service....
But as you know, traveling you are forced to use sporadic data on the road that cost. Until they fix that, I want my storage.
Thank you for starting this thread driving me nuts today! Thought I was alone. It's my son's tablet and Netflix is one of his major uses for it. Tried so many fixes and none are working. Guess we'll keep an eye out for an update.
Also, anyone have trouble with Netflix in general? I had to install an xposed mod just to get it to run!?!
Edit: I tried a much older version of Netflix and it's working perfectly: http://www.apkmirror.com/apk/netflix-inc/netflix/netflix-3-2-0-build-1340-apk/
I then updated the app again and it refused to load at all. Rolled back and turned off auto updates.
How do you turn off auto updates for a single program? I know how to turn it off completely, but is there a way to do it just for Netflix? It's not like we can deny it network connection..
Also does anyone know the last Netflix version that did work? I think it was around December 2014.
I can also confirm that Netflix 3.2.0 build 1340 does work.
NCSUZoSo said:
How do you turn off auto updates for a single program? I know how to turn it off completely, but is there a way to do it just for Netflix? It's not like we can deny it network connection..
Also does anyone know the last Netflix version that did work? I think it was around December 2014.
I can also confirm that Netflix 3.2.0 build 1340 does work.
Click to expand...
Click to collapse
Go to Netflix in the play store then hit the three buttons in the top right and the option to disable auto updates should be there.
Never got around to testing other builds as that on works fine for my kid.
I believe the reason behind new versions beyond 3.7.1 not working is because of below;
"As of version 3.7.2, Netflix has begun using Forced Google DNS lookup for their Android app. This means that the Netflix app bypasses any DNS servers you setup on the Android device or on the router and uses Google DNS instead.
Traditionally we were able to block Google DNS lookups on the router and force Netflix to use alternative DNS. However, the Android app seems to not work at all if Google DNS is blocked."
In any case I can confirm that version 3.7.1 build 1711 does work as it should.
Also as recommended earlier you have to stop the app prom auto updating.
Hope that helps.
So, PayPal and android pay finally integrated. And the only way that the integration will show up in either app is to have play services version 11.0.56. *pic below* However, this update is only supposed to be available to certain parts of the US currently I guess as it was just released about a week ago and they want to soft release.
After I did initial research, I found that I could simply download the updated play services and install. Which worked great initially. (everyone without integration capabilities should be on version 10.x.xx)
Got it set up and properly situated, while on WiFi. Kind of ignored the Google play services won't run unless you update(downgrade) it notification. *pic below*
Went to the store to realize I have no data capability on my phone. Tried just about everything so far besides downgrade because I want the integration.
So to my question vvvvv
*Does anyone know if Google play services/framework is capable of blocking all data traffic? *
Because it still shows I have great data connection(as I use the tmobile lte booster and always have good in home data. Testes with another phone to make sure booster isn't messed up) , but any app I try to use that is connected to Google play, does not have a connection. But everything works perfectly over WiFi
UPDATE: Went to remove my Google account to add it again. Upon removing Google account, sim status shows absolutely no service now
Also, I am on Tmobile
-pulled sim out and back and showing service again. But still not able to access any app connected to play store
Double Update-
**Solved**
For some reason it stopped dns capabilities of ipv6. Which is weird given the apn has been running ipv6 stock in the apn from tmobile... So i switched to my apn which is ipv6/ipv4.
Just still not sure what happened there to make that issue
So I was rooting my Google store bought pixel 4 and missed a step. Needless to say I had to sideload a full ota to recover it. But I'm pretty sure I accidentally loaded the verzion version. I got all the verizon apps that showed up when I rebooted the phone. I went back and wiped everything in recovery mode and tried sideloading QD1A.190821.007.A3 and it keeps erroring out. This is the firmware that Im 90% sure what was on my phone. Is there a way to get back to factory google store firmware or am I screwed now? I am on a verizon sim but phone was bought on launch day from the google store. Its also noted that I am currently on QD1A.190821.014 firmware. This doesn't appear to be the verizon firmware.
The Verizon apps appear not based on which ROM version you load, but instead based on whether you have a Verizon SIM in the phone during setup.
If you loaded the wrong ROM onto the phone, you may not be able to recover by sideloading an OTA. You should be able to recover by doing a complete reflash of the image you want (the image version, not the OTA version).
What error is it giving you?
I cant remember the exact error but it would error out about 45% through the flashing. I am currently running QD1A.190821.014 which appears to the google FI, T'Mobile firmware. I still have the ability to turn OEM Unlock on in my settings, so it appears I am ok. I just wish they had better wording on which firmwares for the unlocked ones form the google store and others.
BubbaGumprc said:
I cant remember the exact error but it would error out about 45% through the flashing. I am currently running QD1A.190821.014 which appears to the google FI, T'Mobile firmware. I still have the ability to turn OEM Unlock on in my settings, so it appears I am ok. I just wish they had better wording on which firmwares for the unlocked ones form the google store and others.
Click to expand...
Click to collapse
Regarding loading the wrong one, I did the same thing because the December update had a discrepancy between the announcement and the download page about which rom applies to which phones. I switched back and forth between QQ1B.191205.011 and QQ1B.191205.012.A1 before they finally corrected it, but everything worked fine on both versions as far as I could tell.
About the Verizon apps, if you're on Verizon or one of its MVNOs, if it installs other stuff, you'll want to leave it. Don't confuse My Verizon and My Verizon Services. My Verizon can be uninstalled, but if you mess with My Verizon Services, you'll end up losing things like wifi calling.
Jon8RFC said:
Regarding loading the wrong one, I did the same thing because the December update had a discrepancy between the announcement and the download page about which rom applies to which phones. I switched back and forth between QQ1B.191205.011 and QQ1B.191205.012.A1 before they finally corrected it, but everything worked fine on both versions as far as I could tell.
About the Verizon apps, if you're on Verizon or one of its MVNOs, if it installs other stuff, you'll want to leave it. Don't confuse My Verizon and My Verizon Services. My Verizon can be uninstalled, but if you mess with My Verizon Services, you'll end up losing things like wifi calling.
Click to expand...
Click to collapse
That's not true. You can go to all apps and show system. MVS can't be deleted without root but you can disable it with no adverse effects. They can't get into your device to see what you have installed and when you installed it, but who wants to give them that info anyway?
bobby janow said:
That's not true. You can go to all apps and show system. MVS can't be deleted without root but you can disable it with no adverse effects. They can't get into your device to see what you have installed and when you installed it, but who wants to give them that info anyway?
Click to expand...
Click to collapse
As of Android 8, disabling My Verizon Services doesn't permit wifi calling because it depended on that application for that functionality. It's hard to remember what else was troublesome, but I thought there was something else which didn't function once it was disabled.
I don't have wifi calling anymore on Visible, and I never used Android 9 because of the wifi scan throttling mess anyway.
Would you mind checking that your wifi calling works on your pixel 4, disabling My Verizon Services, rebooting, switching on airplane mode, then enabling wifi only, and then try making a phone call? I'm interested to know if that behavior has changed. Thanks!
Here's some more information. It certainly seems true for others as well:
https://community.verizonwireless.c...ng-since-Android-8-update/td-p/1042025/page/2
And many other XDA threads correlating the two:
https://www.google.com/search?q=sit...69i57j69i58.6651j1j7&sourceid=chrome&ie=UTF-8
Maybe things have changed in Android 9 or 10, but please test it out if you haven't already!
EDIT:
It looks like you tested it out in another XDA thread already where others lost wifi calling when it was disabled, but you said you were still able to make wifi calls. It's strange that you're the only one who can disable My Verizon Services and make wifi calls, but others can't. Very strange.
Jon8RFC said:
As of Android 8, disabling My Verizon Services doesn't permit wifi calling because it depended on that application for that functionality. It's hard to remember what else was troublesome, but I thought there was something else which didn't function once it was disabled.
I don't have wifi calling anymore on Visible, and I never used Android 9 because of the wifi scan throttling mess anyway.
Would you mind checking that your wifi calling works on your pixel 4, disabling My Verizon Services, rebooting, switching on airplane mode, then enabling wifi only, and then try making a phone call? I'm interested to know if that behavior has changed. Thanks!
Here's some more information. It certainly seems true for others as well:
https://community.verizonwireless.c...ng-since-Android-8-update/td-p/1042025/page/2
And many other XDA threads correlating the two:
https://www.google.com/search?q=sit...69i57j69i58.6651j1j7&sourceid=chrome&ie=UTF-8
Maybe things have changed in Android 9 or 10, but please test it out if you haven't already!
EDIT:
It looks like you tested it out in another XDA thread already where others lost wifi calling when it was disabled, but you said you were still able to make wifi calls. It's strange that you're the only one who can disable My Verizon Services and make wifi calls, but others can't. Very strange.
Click to expand...
Click to collapse
My wife has a Verizon device Pixel 3 locked bl and I have a Pixel 4 and they both have MVS disabled and both can call on wifi. I just tested again to make sure. Really, I'm the only one? Gotta love that. I hate that they can get into my device without my knowing and see what and when I installed stuff.
Anyone facing this problem? My google pay is inconsistent when on public transport and in retail stores.
Could it be software issue?
Can you type Oxygen version, root or no? And can you find in Google play settings certification of you device?
alf_and_co said:
Can you type Oxygen version, root or no? And can you find in Google play settings certification of you device?
Click to expand...
Click to collapse
Also having problem with my NFC with public transport.
Never work for public transport before, but ok with retail payment
my is Oxygen OS 10.5.10.IN11AA, no root.
not sure if this is the Google Play Cert
Version 20.6.19-all [0] [PR] 316598174
OOS 10.5.10.IN11AA
Google Play Services Version 20.21.17
Google Pay Version 2.111.306
I tried toggling on the '' non standard NFC tag support '' in developers option. Doesnt work as well.
Many op8p users also faced the same problem in my country.
Tried re-adding my cards several times, cleared cache of google pay,google play services,google framework.
Downgrading app versions.
On public transport, my phone just vibrates and will prompt " does not work " or " move closer ". Never worked, receiver receive nothing.
In retail payment, it worked about 90% of the time with 10% requiring to tap twice.
I have similar issue.
- I use polish banking application that uses NFC for contactless payment.
- In retail payment, 90% of the time is successful, 10% requires to tap again.
- In vending machine almost every payment is rejected (I got 1 successful payment but I can't reproduce it again). I used same banking application on my xiaomi mi8 with same vending machine and worked good.
- I tried google pay and it doesn't work too (at least it shows some error on screen)
- no root, oxygenos 10.5.9.IN11BA
In conclusion it's not a problem with google pay but with nfc as other payment apps have same problem.
IIRC on the teardown video, the NFC chip is in behind the camera. It's maybe in too deep inside the phone for it to work correctly everytime.
Sent from my IN2023 using Tapatalk
Came looking to see if I was the only one with an NFC issue
Mine has been working perfectly since I got the phone, then yesterday I went to use it at a POS in a shop and it wouldn't work......move closer/slower etc. so I used my bank card itself.
I got the train and said I had low balance when I got off so went to top up my leap card (Irish transport card) and it fails the second it tried to read the card.
FYI I have sucessfully topped up my leap card dozens of times on the phone.
Next I went to get something to eat. I tried using it at the restaurant POS and worked first time, no problem.
Then this morning I just tried using it in shop POS and everytime it pinged and gave me a tick mark and showed the card as if it completed OK but the shop unit did not register anything (I also know the transaction did not go through as revolut did not show the transaction). I used my bank card and it worked.
I have just tried my leap card again and it is still not working.
This is very frustrating as I use NFC payment everywhere.
Anyone know if I can see logs for the NFC chip?
Why did it suddenly just stop working, I haven't had any updates.
Running Oxygen OS 10.5.12.IN11BA
Play services Version 20.33.14(120400-327249014)
Google Pay Version 2.116.328438545
Not had this problem before, could your case be the cause? Or anything else in your hand?
The range has impressed me with mine.
Currently rooted and using xXx and Gpay is still good.
It looks the oneplus 8 pro nfc chip is very weak. For me the strongest signal is under oneplus logo on the back. I found out the nfc chip is under the keypad at vending machine (not under display). Now to make it work I must keep my phone very closely to the terminal.
I need to get close on a number of NFC readers...no biggie.