Related
Based on various news outlet (example: http://www.androidcentral.com/updated-google-wallet-app-coming-all-us-based-android-phones), Google has launched an updated Google Wallet app that will WORK with ALL carriers.
Previously, when I installed Google Wallet on my S4A, starting it will give men an error about my device is "not compatible", which is a given since AT&T pretty much blocked Google Wallet.
The new Wallet app supposed to rectify this problem. I updated today, launched the app and did NOT get the error above. I am now presented with a screen that asked which Gmail account I want to use for the Wallet App.
I selected my primary Gmail account, which I used to purchase apps and other Google subscriptions service and I got a:
"Failed to add account. An error has occurred while adding your account"
My web-based Google Wallet is fine, otherwise I won't be able to pay for stuff in Google Play.
Anyone get the new Google Wallet to work in the S4A?
I assume you did the Wallet hack? That might be why, I installed it with no problems last night. It let me choose my account and everything, no warnings at all. I can't verify that it actually works though, there's nowhere on island I can use it
Avail211 said:
I assume you did the Wallet hack? That might be why, I installed it with no problems last night. It let me choose my account and everything, no warnings at all. I can't verify that it actually works though, there's nowhere on island I can use it
Click to expand...
Click to collapse
No, I use the legit app - downloaded from Google Play.
For your Google Wallet, is your account "Verified" in Google Wallet website? Mine is "unverified"...
I installed it on my I537 last night (or earlier today, I honestly can't remember, bleh) and set everything up but a) I don't have a legit Samsung battery at the moment so no NFC capability anyway (real battery should be here tomorrow, actually), and b) after reading up on the device support at Google's support site it looks as though there are two primary requirements for Google Wallet to function:
1) a device with NFC that is supported by Google Wallet
2) a carrier that supports Google Wallet also
Now, looking over the info again at the following link:
https://support.google.com/wallet/answer/1347934?hl=en
it does show that the Galaxy S4 is eligible which should mean the Galaxy S4 Active is included as well, it's the same basic hardware for the most part but, the issue then becomes is your carrier one that supports it, and according to the info on that page the Galaxy S4 (and by similarity in hardware, the Galaxy S4 Active) is only supported for Google Wallet using Sprint, US Cellular, and Google Play so if you're not using one of those you're/we're out of luck - I use T-Mobile and will test out Google Wallet over the weekend with the new battery. I get why Sprint and US Cellular are mentioned: because they ARE cellular carrier providers, but Google Play isn't so that's somewhat confusing why they'd mention it specifically.
Oh well, hope this clarification helps. I'm sure as time passes more carriers will get on board with Google Wallet - once Google starts pushing that aspect hard, other companies aren't going to have much choice but fall in line and provide support.
It's Google we're talking about here...
lanwarrior said:
No, I use the legit app - downloaded from Google Play.
For your Google Wallet, is your account "Verified" in Google Wallet website? Mine is "unverified"...
Click to expand...
Click to collapse
I don't see anywhere about verified or unverified, but it does show my Nexus 7 and S4A as 'Active' when I look at it on my PC. I didn't see verified or unverified in the app either... Just that the devices are 'active'.
Avail211 said:
I don't see anywhere about verified or unverified, but it does show my Nexus 7 and S4A as 'Active' when I look at it on my PC. I didn't see verified or unverified in the app either... Just that the devices are 'active'.
Click to expand...
Click to collapse
If you go to Google Wallet on the web, click on Settings and you'll see a section called "Verify Identity".
BTW, my Google Wallet works now in my S4 Active.. had to uninstall AVG first then it works. Not sure why... But it seems the last AVG update "broke" certain thing? It even reported Cerberus as trojan now..
lanwarrior said:
If you go to Google Wallet on the web, click on Settings and you'll see a section called "Verify Identity".
BTW, my Google Wallet works now in my S4 Active.. had to uninstall AVG first then it works. Not sure why... But it seems the last AVG update "broke" certain thing? It even reported Cerberus as trojan now..
Click to expand...
Click to collapse
Ahh I found it now. Mine says 'unverified' since I haven't given Wallet my address and such. There are 0 vendors where I live that use NFC readers so I haven't been able to even use Wallet, I just installed it in case I get to go back to the states for a visit.
Glad to see you got it resolved though!
Okay i was just wondering if tap to pay with google wallet works on the note 3 with kitkat i have the kitkat update but my phones unlocked and is on tmobile's network so can any one with a AT&T phone and Original sim confirm if its working or not plz put screen shots id confirmed working
Nope
No , tap and pay will not work on kitkat for the SMN900A due to removal of host card emulation in the build. You cannot use Isis Mobile Wallet either even with build.prop modification and a secure-element enabled SIM.
andersonpaac said:
No , tap and pay will not work on kitkat for the SMN900A due to removal of host card emulation in the build. You cannot use Isis Mobile Wallet either even with build.prop modification and a secure-element enabled SIM.
Click to expand...
Click to collapse
I've had an AT&T Note 3 since January 2014 and ISIS has worked the entire time. The Tap and Pay setting in Google Wallet was greyed out when I had 4.3, and since 4.4.2 was released OTA the setting has been entirely gone in Google Wallet. Is it still true that GW doesn't work for the SM-N900A models? Or am I just using the Google Wallet app wrong?
apraetor said:
I've had an AT&T Note 3 since January 2014 and ISIS has worked the entire time. The Tap and Pay setting in Google Wallet was greyed out when I had 4.3, and since 4.4.2 was released OTA the setting has been entirely gone in Google Wallet. Is it still true that GW doesn't work for the SM-N900A models? Or am I just using the Google Wallet app wrong?
Click to expand...
Click to collapse
No , It's not you. GW has removed Tap and Pay for the NFC hardware that's installed on the SM-N900A. At this point there is no working GW solution to SM-N900A. It's possible that there are drivers written for it in 4.4.4 and will be released and that'd enable HCE
So I just got a Moto X. Out of the box, Google Now hotword detection ("Ok Google") worked perfectly both in Google Now and in the Google Now launcher that I sideloaded. Then, hotword detection randomly turned off. If I uninstall and reinstall updates to the Google Search app, hotword is temporarily fixed, but it won't last more than a day until it turns off again. This happens whether or not Motorola's own Touchless Controls are enabled or disabled.
It seems like some other app is causing it to turn off since a third-party hotword detection app wouldn't work, either, but I've hardly installed any apps since I just got it.
Also, I've already tried the most common suggestions such as ensuring that my voice input language is English (US) and making sure than no Accessibility options are enabled.
Any help to get back hotword detection would be greatly appreciated!
The newest Google search update broke hotword. The only way to keep it working for now is to uninstall the update and not install it again until possibly the next update.
Do you know what the latest version of Google Search is that still supports hotwords so I can grab an apk? When I revert back to the factory version of Google Search, it breaks the Google Now Launcher.
Also, any idea why hotwords would work for a while and then randomly stop. This has happened several times, all while I've had the same version of Search.
Uninstall back to 3.1. Make your changes then install 3.2, this is where Hotword Detection is still there but not selectable and Ok Google works. Now install 3.3, Hotword is no longer there but Ok Google still works. Don't install 3.4, you loose both.
Worked for me twice, I accidentally hit Update All and got 3.4 back, had to start over. I've been back on 3.3 for a week or so and Ok Google still works.
I uninstalled to 3.1 (factory version), and did get hotword back, but I couldn't use the Google Now Launcher. Installed 3.2 and still had hotword, but still not Google Now Launcher. Finally, I installed 3.3, I still had hotword, and the Google Now Launcher worked. But a few hours later, hotword got disabled again.
It doesn't seem like the problem is tied to a version. I've gotten hotword to work with 3.4, but it becomes disabled after a little while of use.
micahmo said:
I uninstalled to 3.1 (factory version), and did get hotword back, but I couldn't use the Google Now Launcher. Installed 3.2 and still had hotword, but still not Google Now Launcher. Finally, I installed 3.3, I still had hotword, and the Google Now Launcher worked. But a few hours later, hotword got disabled again.
It doesn't seem like the problem is tied to a version. I've gotten hotword to work with 3.4, but it becomes disabled after a little while of use.
Click to expand...
Click to collapse
In previous versions of Google search, you could say "Okay Google" instead of "Okay Google Now" to activate the hotword when you had the Google app open? I just recently bought the phone and it came already with the newest version of Google Now installed.
I don't think you've ever been able to say "Ok Google Now" as a hotword to activate voice search in the Google app. "Ok Google Now" is Motorola's keyword for its Touchless Controls. Touchless Controls have always worked for me, but when I'm in the Google app (or in the Google Now launcher that I sideloaded), I prefer to use Google's own hotword, "Ok Google" to activate voice search.
Out of the box, my phone also came with the latest version of Google Now installed, and hotword worked out of the box, but for some reason it became disabled. Any time I uninstall and reinstall Google Search (or even clear data), hotword is restored temporarily, but then becomes disabled again after a while.
Did you leave Touchless Control untrained? I didn't disable it but it is untrained at the moment. My phone is a Developers Edition, unlocked and rooted, if that helps any.
I was able to use the Google Now Launcher on 3.2, maybe it is the version of the Launcher? Mine is 1.0.16.1154249 and I did side load it. I haven't
had any trouble with the hotword detection reverting to off as long as I say on 3.3.
Various threads in different forums say different things about this to being a Chrome problem to a Google Search problem to Motorola disabling it
on purpose so the it doesn't interfere with Touchless Control. I guess I'll have to see what happens when Search 3.5 comes out.
At the moment, I don't have a car so the parking feature doesn't have a relevance for me but setting a timer would be kind of useful.
If is is an accident, it would be nice it it were fixed quickly. If it is on purpose, I really wish someone would re evaluate the policy of not allowing a
function on a device that I purchased and would like to make the decision for my self. Just my opinion.
I do hope you find your solution. I came from a Galaxy Nexus and I have been really liking this phone so far as it is as close to the stock that the
GNex was.
SoloDB said:
Did you leave Touchless Control untrained? I didn't disable it but it is untrained at the moment. My phone is a Developers Edition, unlocked and rooted, if that helps any.
Click to expand...
Click to collapse
No, I did train Touchless Control. I could try disabling it and then re-enabling it without training it, but I don't see how that would fix anything. I actually like using Touchless Control for when the phone is out of my reach (which is exactly what it's for), but it's kinda slow and doesn't always respond. Ideally, I'd like to use both Touchless Controls and Google's hotword.
My phone is the unlocked T-Mobile version and unrooted. I don't know if that makes a difference.
I was able to use the Google Now Launcher on 3.2, maybe it is the version of the Launcher? Mine is 1.0.16.1154249 and I did side load it.
Click to expand...
Click to collapse
My launcher version is 1.0.9.1039417, but I grabbed an APK of the same version you have and it still didn't work with Google Search 3.2.
Anyway, maybe an update to Google Search or Touchless Controls will fix it eventually.
According to Moto, the disabled this as it conflicts with Touchless Controls. I think that's BS, but whatever.
I was having a conversation with my fiancé earlier and Google Now popped up when I said "Ok, you" in conversation. I appreciated Google's sentiment.
Sent from my Moto X
natezire71 said:
According to Moto, the disabled this as it conflicts with Touchless Controls.
Click to expand...
Click to collapse
TBH, this is the most likely explanation, since, no matter what version of Search I use, hotword works for a little while and then gets disabled. I even installed a third-party hotword-listening app, and it was disabled immediately. Really hope Moto rethinks this.
micahmo said:
TBH, this is the most likely explanation, since, no matter what version of Search I use, hotword works for a little while and then gets disabled. I even installed a third-party hotword-listening app, and it was disabled immediately. Really hope Moto rethinks this.
Click to expand...
Click to collapse
I've raised this issue multiple times over on the Motorola Forums. The Forum Manager there told me that's what Motorola told him. It's unfortunate.
natezire71 said:
I've raised this issue multiple times over on the Motorola Forums. The Forum Manager there told me that's what Motorola told him. It's unfortunate.
Click to expand...
Click to collapse
It sounded like he was going to bring it up and submit a report on the issue, using the conversation in the Motorola forums as a basis. It'd be nice if that led to hotword being re-enabled but who knows. Sounds like some software update is on the way, at least for t-mobile; maybe that will help. Wishful thinking...
Maybe 4.4.3 but who knows.
Google Now Hotword
If your phone is rooted, I think I have a solution for you. It's been working on my phone for about a day now. I don't think I have enough posts in to do any links, but if you go to Droid Life and read the article under "Google Makes “Ok Google” System-wide Hotword Detection Official" the is a link in the comments to a utility called UnLeashTheGoogle. Follow the instructions to get the Google Now stuff working. There is an added step however, look for hotword_blacklisted_devices and change the XT1060 to anything else, I used XT1000. I also went as far as disabling the Touchless Control app so that it wouldn't interfere with the Google Now functions.
All of you that use Touchless Control, great, it is a neat feature, but I prefer to use a more Nexus like feel. To each his own.
SoloDB, that would be a great solution if I were rooted. It's almost tempting enough, although I don't feel like wiping my device at this point.
It's sad that even with the rollout of Google Now's always listening feature, it's still disabled on the Moto X. And it's obviously intentional since the device is blacklisted.
micahmo said:
SoloDB, that would be a great solution if I were rooted. It's almost tempting enough, although I don't feel like wiping my device at this point.
It's sad that even with the rollout of Google Now's always listening feature, it's still disabled on the Moto X. And it's obviously intentional since the device is blacklisted.
Click to expand...
Click to collapse
You can root using pie via the moto x toolkit without wiping anything. I just did this the other day, but I deleted everything from the blacklist section.
The only issue I'm having now is always listening via Bluetooth in my car (2013 Honda crz hands free link non-nav). It worked flawlessly with my galaxy nexus.
Yes, unfortunately you have to have root. The utility needs root and before I found UnleashTheGoogle I edited the Google Search app pref file to
alter the blacklist which got Ok Google working in the first place, I needed root for that as well being the folder is in the System area. The utility
got everything enabled as well.
I know there are security issues having a rooted phone, but I learned in the Galaxy Nexus days how valuable it is to have a bit more control of
the phone to do the kind of stuff you'd like to do other than what Verizon and, in the case of the Moto X, the manufacturer would "prefer" you to do. The Developers Edition of
Moto X really has made the transition away from the old Galaxy Nexus really easy.
I wish I could root but my work email policies check for that.
Sent from my XT1053 using Tapatalk
txaggies07 said:
I wish I could root but my work email policies check for that.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Would this help? http://repo.xposed.info/module/com.phantasm.xposed.gfesecuritypatcher
Anyone else recently get updated to the new Android Pay / Google Wallet app combo? Since the update, I haven't been able to get Pay working. I'm logged in with my Google account, it sees the cards I have on my Wallet account, but when I select one it will sit and think for a while before spitting out:
Android pay cannot be used
Google is unable to verify that your device or the software running on it is Android compatible
Click to expand...
Click to collapse
And it only gives me an option to dismiss the dialog.
This worked fine on 4.4.4 and 5.0.2.
I may have an APK of the old Google Wallet somewhere, thinking I'm downgrade to that and see how it goes.
Anyone else see this?
edit: should have googled first, this is because the phone is rooted (which I kind of suspected). The simple solution is to temporarily disable root, add your cards, then re-enable root.
I rooted my phone when i had it, so now, im unable to connect to my samsung account. Anyone can help me ?
J_O said:
I rooted my phone when i had it, so now, im unable to connect to my samsung account. Anyone can help me ?
Click to expand...
Click to collapse
perhaps you're having the same problem as i do, mine is outdated kernel. after updated the kernel, i'm all good. i'm using TGP rom with tgp permissive kernel.
Samsung not allowing logging into Samsung account on rooted phones
The exact same thing is happening to me after the last firmware update. On the old firmware, it was possible to log into one's SAMSUNG account to re-download previously purchased items from the Galaxy Store. Since the July 1st, 2019 security patch, SPAMDUNG have elevated their harassment of rooted customers to a new level:
Every time one tries to enter the user credentials (e-mail address and password for the Samsung account), the phone goes to the Legal Information page with the terms and conditions. After accepting them, a field at the bottom pops up, asking whether one would like to use biometrics for identification. No matter whether one chooses «not now» or «register», a black square appears between the two possible answers to the biometrics question, informing the user that «processing failed». Sometimes, the following error message is shown in the white field at the bottom of the screen ...
Account
Unknown error
(DataNull0/A300103)... before being taken back to the account settings with the field for the Samsung account's e-mail address and password. From there, one could play the scenario over and over again ad infinitum, but without any hope of ever getting out of this «login loop».
To make matters worse, as soon as one enters one's e-mail address in an attempt to log in, the Samsung Experience Service sends the following notification in 15 min. to 1 hour intervals, and they cannot be turned off in the configuration settings:
Samsung account
To continue using services securely, sign in again.When trying to «Continue with Google»:
To continue, sign in to your Samsung account again.The suggestions that one can find on the Internet to at least get rid of the nerve-killing notification messages are:
Settings | Developer Options | Running Services
Samsung Experience | Notification Listener | Settings | Notification Access
Samsung Experience => turn this off!!
Settings | Apps | ⁞ (upper right corner) | Show System Apps | Samsung Account => turn off Notific., uninstall updates
Navigate to http://findMyMobile.Samsung.com. Login, accept the terms & conditions, reboot the phone, voilà.
None of them work.
To disable SPAMDUNG Galaxy Apps notifications:
Open the Samsung folder and the Galaxy Apps therein.
Tap the ⁞ menu (three vertical dots to access more options) in the upper right corner.
Tap «Settings», then «Notifications» and slide the button to «off».
Samsung's notifications should now no longer bother you, but that does not solve the underlying problem.
This leads to the questions:
How to overcome the impertinence that SPAMDUNG harass their customers with and log into one's SPAMDUNG account on a rooted phone?
Alternatively, how to back up the purchased fonts, themes, etc., that were acquired from the Galaxy Store from an unrooted phone to an external SD card or Windows PC, in order to re-install them to the rooted phone later?
Thank you for any pointers to solutions that allow to update rooted phones every month, in a manner that preserves the software one has paid for as well as the configuration settings, apps, their data and so on.
Qui Peccavit said:
The exact same thing is happening to me after the last firmware update.
Thank you for any pointers to solutions that allow to update rooted phones every month, in a manner that preserves the software one has paid for as well as the configuration settings, apps, their data and so on.
Click to expand...
Click to collapse
Thank you for your post. I've been evaluating if I want a Samsung Account. I am not rooted, but I am using the US UNLOCKED U1 firmware. I have it locked on Oreo so my line-of-business software can work, and blocked the play store security policy malware and auto-updates from there so I can use my phone productive. There are few carrots for me to want a Samsung account:
1. Samsung Pay
2. A few nice apps.
However, if sign up for a Samsung account, will I be required to update to their latest crippling firmware/malware, and the latest play store security policy malware? I can't afford to be forced into cow Pie and the latest play store security policy malware.
Thanks!
IT_Architect said:
Thank you for your post. I've been evaluating if I want a Samsung Account. I am not rooted, but I am using the US UNLOCKED U1 firmware. I have it locked on Oreo so my line-of-business software can work, and blocked the play store security policy malware and auto-updates from there so I can use my phone productive. There are few carrots for me to want a Samsung account:
1. Samsung Pay
2. A few nice apps.
However, if sign up for a Samsung account, will I be required to update to their latest crippling firmware/malware, and the latest play store security policy malware? I can't afford to be forced into cow Pie and the latest play store security policy malware.
Thanks!
Click to expand...
Click to collapse
I salute you for being still on Oreo as me yes, you can download updates and everything from play store and also from Galaxy store without needing any firmware update or going to Pie Oreo forever!
Da-BOSS said:
I salute you for being still on Oreo as me yes, you can download updates and everything from play store and also from Galaxy store without needing any firmware update or going to Pie Oreo forever!
Click to expand...
Click to collapse
1. Do you use Samsung Pay?
2. I do manual updates of specific apps from the play store because call recording apps that uses the call logs to document call recordings using the phone number and contact name no longer work thus destroying its functionality. They not only destroy their ability going forward, they also destroy the history. This was caused by the play store updates, which they force on developers. Thus, you must download previous versions from apkpure.com etc., or have a backup copy, which is what I have. The other side I need to protect myself from is their "Security Policy Updates"/play store malware, that freezes app my older call recording apps. Thus, play store automatic updates and their "Security Policy Upates" make the play store less honorable that those who write ransomware because at least with them you can pay to get your data back while you cannot do with the play store.
3. You can record calls on Pie, but with any version of Pie, the call recording quality is terrible while the same phone flashed to Oreo is crystal clear.
4. Android 10/Q/Quicksand or whatever update stops call recording altogether so now the only ones with recordings of your phone calls, call logs, texts, and contact lists, are your phone manufacturer, wireless carrier, Google, the NSA, and anyone who will pay a nickle to have access to them, as long as they aren't the same people who participated in the conversations. Another "feature" of the Android 10/Q/Quicksand update is it kills Android Beam for exchanging data. However, in exchange for killing these capabilities they give you "long-awaited system-wide dark mode", which you could make happen on even Note 3s and 4s until they took it away, to where you needed 3rd party app, and now you don't need a 3rd party app because they are giving it back as a new feature.
5. A Note 9 frozen to Oreo with blocked "Security Policy Updates" is worth far more than a Note 10+ and beyond will ever be. You want to do frequent backups with matching pre-2019 APK and Windows versions of backup software such as SmartSwitch, and another backup software in case you want to switch to another brand phone later. That way if they slip in some of their ransomware 2.0 or other malware, you can re-flash and restore your phone to full functionality.
The way someone can determine if they have a diseased version of Oreo is to download the call recording app, "Automatic Call Recorder" by Appliqato from APKPure that is version v5.43.11 or older. If Oreo allows you to install it, make a call to and from your phone from a contact in your contacts list. If the app doesn't freeze, go into the call recorder and check your recordings. If you do not see the name of the person you called or who called you, then you have the disease and need to re-flash Oreo. See Restore Call Recording to your Note 9 SM-N960U and SM-N960U1 to stay safe from malware authored authored by the carrier and play store. Simply because they are incorporated or are a government-run clandestine operation doesn't make them honorable. The same can be said for Mafia's businesses and the government of Democratic People's Republic of Korea, which is neither democratic nor belongs to the people. In the US, the Edward Snowden revelations, FISA court violations, and deep-state investigations, leaks, social media "oppsies" prove that you need to do your own due-diligence because with regard to security because you are the product being bought and sold like a pack of cigarettes to fund Google, Android, IOS, apps, agendas, etc.
From what I know once you have rooted your Samsung device. You will not be able to connect to any Samsung services via that device.
jalanbesi said:
perhaps you're having the same problem as i do, mine is outdated kernel. after updated the kernel, i'm all good. i'm using TGP rom with tgp permissive kernel.
Click to expand...
Click to collapse
So you're saying that it is possible to use and login to samsung account on a rooted device ??? My backups are there and I can't restore my phone because of that. Is there a way to do it. ???
Just try deleting all the cache and data on all the Samsung apps I used *link2sd* then rebooted worked for me ?*