Has this happened to anyone else?
It seems like this has been happening for the Galaxy Nexus as well:
http://forum.xda-developers.com/showthread.php?t=1657935
I am on CM9 nightlies with my NS4G. I updated google wallet this morning and had it ask for superuser access. Seems like from the thread above people have been able to use it with both a deny and an allow. Also from the thread above: Google Wallet CS# is 855-492-5538 so we can also bug them about why google is doing this.
Related
I am running the stock v2.3.4 build GRJ22 on my ns4g, but can't seem to find some apps on the market. Specifically, Google Listen, Google Goggles, Facebook for Android, HandyCards-Rewards.
Any idea why they are not showing up. I have seen in some other forums that people have them on their NS4Gs. Do I have to root it for these to work?
One of the other device forums mentioned having to do a factory reset. Is that the only option?
Pure stock? Did you root it or anything?
anesone said:
I am running the stock v2.3.4 build GRJ22 on my ns4g, but can't seem to find some apps on the market. Specifically, Google Listen, Google Goggles, Facebook for Android, HandyCards-Rewards.
Any idea why they are not showing up. I have seen in some other forums that people have them on their NS4Gs. Do I have to root it for these to work?
One of the other device forums mentioned having to do a factory reset. Is that the only option?
Click to expand...
Click to collapse
try going to market.android.com and downloading them from there
If its not showing it probably isnt supported with gingerbread. Although some apps might "work"
Uncle Jimmy says hello
I have experienced this quite a bit, and it is very frustrating to say the least. Essentially the market filters out "incompatible apps" based on the android version. However I would rather be able to download it and decide for myself whether it is compatible or not.
Nevertheless there is no way around it (that I could find). Myself and all the other cm7 users have experienced this since running cm7...
I would imagine there is a way to bypass it, but who knows how and how difficult it would be for that matter.
Try the following apps;
Market enabler
or
Market Doctor (by Tibu)
may fix your problem
awsome..trying now!
Sent from my Nexus S 4G using XDA App
Hey guys first time posting here, but have been reading up lately after getting this issue on my S3 i747 with AOKP ROM.
Did the auto update from my phone and it seemed to apply but now I cannot launch the Play Store, Gmail app or sign into my YouTube. When trying to launch the Play Store it tries, then crashes, same with Gmail. When I try to sign into YouTube by clicking on the sign-in option, it just fails. The biggest concern I have is that I cannot see Google on my list of accounts to sync in settings.
After reading some of the dev forums here I get the idea that I may need to reflash my gapps? But not sure how to do it or if that will in fact fix my issue. I don't know if I have a back up on the phone as I had a friend do the rooting for me.
Really appreciate what you guys are doing here for newbies like me. Hope someone can help!
mo91 said:
Hey guys first time posting here, but have been reading up lately after getting this issue on my S3 i747 with AOKP ROM.
Did the auto update from my phone and it seemed to apply but now I cannot launch the Play Store, Gmail app or sign into my YouTube. When trying to launch the Play Store it tries, then crashes, same with Gmail. When I try to sign into YouTube by clicking on the sign-in option, it just fails. The biggest concern I have is that I cannot see Google on my list of accounts to sync in settings.
After reading some of the dev forums here I get the idea that I may need to reflash my gapps? But not sure how to do it or if that will in fact fix my issue. I don't know if I have a back up on the phone as I had a friend do the rooting for me.
Really appreciate what you guys are doing here for newbies like me. Hope someone can help!
Click to expand...
Click to collapse
Download gapps and flash it in cwm. It's probably located in the OP of your ROM
So basically I got my Nexus 5 a month ago and from day 1 I could not access Google Now by swiping right on the homescreen. However, "Okay Google" does work.
I have checked my Location Settings and it says that Google Location Reporting is not available in Malta. I do not assume this is the problem since my Maltese friends have Google Now and it work perfectly (not the ones with Nexus 5).
I am running 4.4.2. and I just got the Google + and Google Search updates last night which I installed. Still no Google Now. I cannot even access the settings for Google Now.
I have searched for possible solutions on the internet and there was one post on Google Forums with a bunch of people complaining about this problem but I decided to post on here becase
Maybe we could come up with a possible solution (hopefully one that does not inculde downgrading Google Search)
and secondly to pass on this message. It seems like XDA is a good framework to have complaints go across seeing as Google and LG decided to act on their faulty devices thanks to an XDA thread. (correct me if I'm wrong?)
Hi all,
I have Google Wallet Tap & Pay set up and selected under the settings, despite this nothing really happens when I try to make payments using this. I am on Android 4.4.4 (CM11 Nightly, and Carbon before this), NFC was on and I've tried this at several locations by now.
Before when Tap & Pay didn't work on Verizon I never even got the option to set it up, and but I was under the impression that it did work now. How do I get it to work?
Thanks !!
Google Wallet Tap and Pay No Freaking Worky!!!
GrinReaper said:
Hi all,
I have Google Wallet Tap & Pay set up and selected under the settings, despite this nothing really happens when I try to make payments using this. I am on Android 4.4.4 (CM11 Nightly, and Carbon before this), NFC was on and I've tried this at several locations by now.
Before when Tap & Pay didn't work on Verizon I never even got the option to set it up, and but I was under the impression that it did work now. How do I get it to work?
Thanks !!
Click to expand...
Click to collapse
The issue is that Google does not support custom roms, with KitKat they stopped doing so. I have the same issue you have I am running ATT S3 and the version of wallet my phone is allowed to download is wallet V2.0-r163-v1--release. After talking to Wallet support they said my phone was suppose to have Wallet v.2.0-r172-v6. My guess is that even though my current version allows you to set up tap and pay, it at the same time does not turn on the NFC feature for wallet to recognize the credit card terminal. The NFC is suppose to be used as the triggering device to tell the HCE to listen for transaction information. HCE is software based so it has no hardware to tell it when to process, so it needs NFC to tell it to do so.
Please can someone share wallet v2.0-R172-v6 I would like to try loading it directly to see if that may work.
I have the same version (v18 rather than v1 though)
This is an interesting bit of information, I wonder if the same version works for vzw.
terrylbs said:
The issue is that Google does not support custom roms, with KitKat they stopped doing so. I have the same issue you have I am running ATT S3 and the version of wallet my phone is allowed to download is wallet V2.0-r163-v1--release. After talking to Wallet support they said my phone was suppose to have Wallet v.2.0-r172-v6. My guess is that even though my current version allows you to set up tap and pay, it at the same time does not turn on the NFC feature for wallet to recognize the credit card terminal. The NFC is suppose to be used as the triggering device to tell the HCE to listen for transaction information. HCE is software based so it has no hardware to tell it when to process, so it needs NFC to tell it to do so.
Please can someone share wallet v2.0-R172-v6 I would like to try loading it directly to see if that may work.
Click to expand...
Click to collapse
The version you mention was pushed to my phone today as an update. Haven't tried it yet.
New Google Wallet Update v2.0-R172-v18-RELEASE
GrinReaper said:
The version you mention was pushed to my phone today as an update. Haven't tried it yet.
Click to expand...
Click to collapse
Thanks for the heads up I too have received the update listed above yesterday but have not tried it yet. I will post results later today. I have had broken hope so many times now I think I would **** in my pants if it did work.
Also just a note the update has brought back gift cards in which they removed for a while. The UI is also more streamlined.
Please if this update works for anyone please post.
Thanks..
New Google Wallet Update v2.0-R172-v18-RELEASE Clearly CM 11 issue!
terrylbs said:
Thanks for the heads up I too have received the update listed above yesterday but have not tried it yet. I will post results later today. I have had broken hope so many times now I think I would **** in my pants if it did work.
Also just a note the update has brought back gift cards in which they removed for a while. The UI is also more streamlined.
Please if this update works for anyone please post.
Thanks..
Click to expand...
Click to collapse
I just confirmed that new release Google Wallet Update v2.0-R172-v18-RELEASE does not work at check out. Terminal is not recognized. This is clearly a CM 11 issue. I am running AT&T S3 there is a factory update for my phone that is compatible with google wallet. my guess is that CM is slacking on the S3 as they combined multiple phone to one release and stable version as of yet coming upon a year now, snapshots and nightlies only.
CyanogenMod please fix Google Wallet HCE support for S3 ATT! NFC is not detecting HCE transaction.
Hi, this problem isn't related to Android or Google Wallet version. There is carrier and device restrictions:
http://www.androidcentral.com/google-wallet-tap-and-pay-can-work-any-android-44-device-still-requires-us-sim
Hi, I've recently installed LOS 18.1 for MicroG. All is fine but I can't get my galaxy watch 4 to work with it; I can't get it to finish the pairing with the Galaxy Wearable app.
I've been looking around and found very little information about this.
Is it known not to work or is there something extra I need to do?
Some more info about the setup:
a) MicroG has enabled:
1. Google device registration
2. Cloud messaging
3. Location modules (mozzilla and nominatim)
b) but has disable:
1. Google safetyNet
2. No google account is logged in
c) All the self-check are checked
Thank you for your support.
Have you solved this? I have the exact same issue but i have a google account logged in. This is the only thing holding me back from removing GAPPS.
k1riak100 said:
Have you solved this? I have the exact same issue but i have a google account logged in. This is the only thing holding me back from removing GAPPS.
Click to expand...
Click to collapse
No, I have not found a solution. My watch has been off since I made I switch.
It's a little sad that no one has answered at all to my post.
Also having the same issue, on LOS 20 with MicroG... it looks like I might have to give up microG... too many things not working as expected
I had massive issues authenticating earlier as well, since my Google account kept defaulting to 2 factor.
To answer my own question and since people keep coming back to this thread I thought to give some info:
You can find the state of the MicroG API here -> https://github.com/microg/GmsCore/wiki/Implementation-Status
In our case we should look at the API for wearable. As of today 20th of April 2023, the status is "No functionality is implemented at all".
Additionally there's a bounty to add support for the wearable API. You could tip in if you would like someone to work on it. You can find this here -> https://github.com/microg/GmsCore/issues/4
So to my original question: there's nothing that can be done about wearables with MicroG. It is known not to work as the community hasn't had resources to work on reimplementing this part of the API.