Hier everyone
When I use my payment app, "ma carte" which includes paylib app for NFC payments, I don't find the way to make it work. I used this app whithout any problem on other phones. I can launch the app but the option to pay without contact doesn't appear...
If anyone could help me I would like appreciate,?
I hate to ask the obvious, but do you have NFC enabled, and are you aware that it's behind the camera screens?
Archer said:
I hate to ask the obvious, but do you have NFC enabled, and are you aware that it's behind the camera screens?
Click to expand...
Click to collapse
Of course
fax11 said:
Of course
Click to expand...
Click to collapse
Cool - that's the easy stuff ruled out then. Hope you get it sorted
Solved
After many installations,and a few days it worked...
fax11 said:
Solved
After many installations,and a few days it worked...
Click to expand...
Click to collapse
Hey !
Question : Did you root your phone ?
I'm on OnePlus 6 but it's probably the same.
My bank (CIC) have enabled PayLib through LyfPay app two days ago, used it without problem to buy a beer, but rooted the phone yesterday after this, switched to Franco Kernel.
Magisk indicates that both SafetyNet tests are successful and Magisk is hidden from my bank app and LyfPay, but the PayLib section in the LyfPay app doesn't appear anymore ... Mhhh
Looks like it detected rooting although everything seems fine and hidden ... That's what i ask if you rooted, to see if it's not just an app or service bug and if it could resolve in a few days
Totone56 said:
Hey !
Question : Did you root your phone ?
I'm on OnePlus 6 but it's probably the same.
My bank (CIC) have enabled PayLib through LyfPay app two days ago, used it without problem to buy a beer, but rooted the phone yesterday after this, switched to Franco Kernel.
Magisk indicates that both SafetyNet tests are successful and Magisk is hidden from my bank app and LyfPay, but the PayLib section in the LyfPay app doesn't appear anymore ... Mhhh
Looks like it detected rooting although everything seems fine and hidden ... That's what i ask if you rooted, to see if it's not just an app or service bug and if it could resolve in a few days
Click to expand...
Click to collapse
I sent you a private message
Totone56 said:
Hey !
Question : Did you root your phone ?
I'm on OnePlus 6 but it's probably the same.
My bank (CIC) have enabled PayLib through LyfPay app two days ago, used it without problem to buy a beer, but rooted the phone yesterday after this, switched to Franco Kernel.
Magisk indicates that both SafetyNet tests are successful and Magisk is hidden from my bank app and LyfPay, but the PayLib section in the LyfPay app doesn't appear anymore ... Mhhh
Looks like it detected rooting although everything seems fine and hidden ... That's what i ask if you rooted, to see if it's not just an app or service bug and if it could resolve in a few days
Click to expand...
Click to collapse
Same here.
My bank app detect root and so I can't pay with gpay or bank app by nfc
If you are not seeing the option to make NFC payments in your "ma carte" app, there are a few things you can try to troubleshoot the issue:
1# Make sure that NFC is enabled on your phone. You can check this by going to your phone's settings and looking for the NFC option.
2# Ensure that your phone is compatible with the "ma carte" app and paylib app for NFC payments. Check the app's documentation or contact their support team to confirm.
3# Verify that your "ma carte" app and paylib app are up to date. Check the app store for any available updates and install them if necessary.
4# Try removing and reinstalling the "ma carte" app and paylib app to see if that resolves the issue.
5# Check if there are any conflicting apps or settings on your phone that may be interfering with NFC payments. For example, some antivirus apps or battery optimization settings may prevent NFC from functioning properly. Try disabling any such apps or settings temporarily to see if that resolves the issue.
6# If none of the above steps solve the problem, contact the "ma carte" and/or paylib support team for further assistance. They may have additional troubleshooting steps or be able to identify any specific issues with your account or device that are preventing NFC payments from working properly.
Related
I've been searching for the past 24 hours (almost non-stop) for a way to make Google Wallet work on my phone. And I still haven't been able to find one for the Nexus 4. Other devices, I have... but I don't know if those will work (i.e. GS4 fix will work on N4?).
I'm currently running Illusion v2 Beta. And every time I try to just open up GW to set it up... I get this screen (attached image).
Before I rooted and everything, it was running perfectly. I've uninstalled it. Reinstalled. Cleared data/cache. Tried on WiFi and on Mobile Data... and still nothing works.
So how do I get Google Wallet to work on my phone?
jbdavies said:
I've been searching for the past 24 hours (almost non-stop) for a way to make Google Wallet work on my phone. And I still haven't been able to find one for the Nexus 4. Other devices, I have... but I don't know if those will work (i.e. GS4 fix will work on N4?).
I'm currently running Illusion v2 Beta. And every time I try to just open up GW to set it up... I get this screen (attached image).
Before I rooted and everything, it was running perfectly. I've uninstalled it. Reinstalled. Cleared data/cache. Tried on WiFi and on Mobile Data... and still nothing works.
So how do I get Google Wallet to work on my phone?
Click to expand...
Click to collapse
Have you tried uninstalling it and using Mocados mod? You can find it here: http://www.modaco.com/topic/354635-xmod-region-device-root-patched-google-wallet/
When using Google wallet and changing ROMs you have to reset wallet before you change, read more about it in the link, its an Xposed mod.
22sl22 said:
Have you tried uninstalling it and using Mocados mod? You can find it here: http://www.modaco.com/topic/354635-xmod-region-device-root-patched-google-wallet/
When using Google wallet and changing ROMs you have to reset wallet before you change, read more about it in the link, its an Xposed mod.
Click to expand...
Click to collapse
I have. And not even that worked for me.
Three things to note:
1) Are you near Salt Lake City? T-Mobile issues ISIS SIM cards in Salt Lake City and Austin (beta test market) which are known to conflict with Google Wallet. You will need a NON ISIS SIM card for Google Wallet.
2) Rev 11 phones had a known issue (like mine), which required contacting Google with a debug log. Within a week or two, they will fix the Secure Element initialization issue on their backend.
3) The latest market version has had issues for some with custom (rooted) ROM's. Try an older APK, or stock ROM.
SpookyTunes said:
Three things to note:
1) Are you near Salt Lake City? T-Mobile issues ISIS SIM cards in Salt Lake City and Austin (beta test market) which are known to conflict with Google Wallet. You will need a NON ISIS SIM card for Google Wallet.
2) Rev 11 phones had a known issue (like mine), which required contacting Google with a debug log. Within a week or two, they will fix the Secure Element initialization issue on their backend.
3) The latest market version has had issues for some with custom (rooted) ROM's. Try an older APK, or stock ROM.
Click to expand...
Click to collapse
I am in Salt Lake City, but my sim card doesn't say ISIS... which I think they always do? Mine doesn't say anything.
I'll try and find an older Wallet apk and see if that helps.
If not, guess I'll be submitting a bug report to Google.
Thanks for the info.
jbdavies said:
I am in Salt Lake City, but my sim card doesn't say ISIS... which I think they always do? Mine doesn't say anything.
I'll try and find an older Wallet apk and see if that helps.
If not, guess I'll be submitting a bug report to Google.
Thanks for the info.
Click to expand...
Click to collapse
Try this one: http://forum.xda-developers.com/showpost.php?p=37299470&postcount=3182
SpookyTunes said:
Try this one: http://forum.xda-developers.com/showpost.php?p=37299470&postcount=3182
Click to expand...
Click to collapse
That still didn't work.
How do I go about submitting a bug to Google about this? Do I have to do it from the phone?
jbdavies said:
How do I go about submitting a bug to Google about this? Do I have to do it from the phone?
Click to expand...
Click to collapse
This applies to stock Android, as Google has no way to fix an issue in a third party ROM. If you flash back to stock 4.2.2 and still have the issue, then this is the process Google sent to me:
1. On your phone/tablet go into Settings, About Phone, tap "Build Number" seven times. Developer options will then appear in Settings.
2. Go into Developer Options and enable Developer Options (ON/OFF switch at the top), then enable "USB Debugging" (near the bottom of the screen).
3. Nexus devices: Press and hold volume down + and volume up buttons. Now also press and hold power button until you can feel the phone vibrate.
4. In about 20 seconds, you'll get a double buzz. A Gmail message dialog should appear. Please email the bug report to yourself and then attach it to your email and send it off to [email protected]
Maybe its the ROM your running? I have actually switched between ROMs and have never reset my Google wallet. It just always works .
Sent from my Nexus 4 using xda app-developers app
PJcastaldo said:
Maybe its the ROM your running? I have actually switched between ROMs and have never reset my Google wallet. It just always works .
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I've thought about that. Just haven't felt like switching... because I'm lazy like that. Haha.
But if a fix doesn't come up in the next day or so... I wont have a choice.
Had the same problem a month ago. As stated in the earlier post you got to call Google and send the log cat. They walked me through it over the phone took about a week for them to fix it and then they gave me a 20 dollar play store credit. Still spending that 20 dollars about 8 dollars left to buy more apps.
I couldn't get google wallet to work for like a month. i try today after seeing this post and it works. crazy.
I did call google in the past and they asked for the log but i never sent it.
Alright guys,
Essentially I'm having a little problem with my S Health App, I am on the rooted N9100f phone with the Echoe rom installed.
every so often my S Health app seems to reset my profile to a Jame Lee born 01 Jan 1970, 4' 11" and 110lbs. I feel sorry for the human if he does exist but I'm not sure why this is happening. Does anyone have any experience with fixing this or just it happening to them.
Also I don't seem to be about to restore to a backed up S Heath profile which is kind of weird.
Anyways Cheers in a advance
I'm sorry to have to tell you this, but you have multiple personality disorder, and are changing it yourself.
Sorry, no clue.
That's because you are James Lee.... you've always been James Lee <que dramatic music>
Sent from my SM-N910P using Tapatalk
Same problem
Kofeye: My unrooted S5 did the same thing late yesterday after successfully tracking weight, steps, heart rate for several months.
S Health "James Lee" Problem
Some of you use xmodgames? I think this is the problem. I get the same problem, when i uninstall the app, I dont get any errors on S Health.
kofeye said:
Alright guys,
Essentially I'm having a little problem with my S Health App, I am on the rooted N9100f phone with the Echoe rom installed.
every so often my S Health app seems to reset my profile to a Jame Lee born 01 Jan 1970, 4' 11" and 110lbs. I feel sorry for the human if he does exist but I'm not sure why this is happening. Does anyone have any experience with fixing this or just it happening to them.
Also I don't seem to be about to restore to a backed up S Heath profile which is kind of weird.
Anyways Cheers in a advance
Click to expand...
Click to collapse
It's not xmodgames, as I don't have that installed on this phone and never did.
I have the exact same issue. I highly suspect it is one of the root apps messing with some background Samsung service which S Health requires to work properly. Will be watching this thread and trying to figure out what exactly causes this. I hope we get to the bottom of this soon.
fahadysf said:
It's not xmodgames, as I don't have that installed on this phone and never did.
I have the exact same issue. I highly suspect it is one of the root apps messing with some background Samsung service which S Health requires to work properly. Will be watching this thread and trying to figure out what exactly causes this. I hope we get to the bottom of this soon.
Click to expand...
Click to collapse
I don't have my s5 active rooted or x mod games and see this James Lee issue now too on S Health. Could it be default values set by samsung dev when app is reset?
This happens when xposed framework is being installed cause it has issues with S-health secure server. It is a need of disabling s-health server security to make the phone work with xposed without issues. Everytime xposed get reinstalled the S-health app resets. You then got to install the backup from your S-health sync service and all is well. Rmember to sync just before updating or installing xposed (or Roms with xposed) to not loose data.
Wanam xposed kit has this option to deactivate secure server to make xposed framework function well with phones having S-health. Most custom rom implements xposed framework and then probably also need to disable secure server.
Edit. To be able to sync/backup S-health, aecure server must be disabled first by installing Wanam kit or other xposed apps with this option. Many custom roms also implements Wanam features.
Sent fra min SM-N910F via Tapatalk
For the past two days I have been experiencing force closes of the Settings app whenever NFC and Payment is selected, due to this I'm currently unable to turn on the NFC option in order to use Android Pay and (or) Samsung Pay. Has anyone else been experiencing this or might have some advice on what the issue may be?
Thanks
glm0025 said:
For the past two days I have been experiencing force closes of the Settings app whenever NFC and Payment is selected, due to this I'm currently unable to turn on the NFC option in order to use Android Pay and (or) Samsung Pay. Has anyone else been experiencing this or might have some advice on what the issue may be?
Thanks
Click to expand...
Click to collapse
Have you disabled any apps? Maybe clear data on the NFC app?
benbailey84 said:
Have you disabled any apps? Maybe clear data on the NFC app?
Click to expand...
Click to collapse
Thanks for the advice, I'm currently using Package Disabler Pro and I had several apps disabled although I had unmarked the NFC service it would still be disable, I had to uninstall the app and reinstall, un-check NFC service and was able to access NFC and Payment. Guess it was an error on my side.
Hi all!
I'm writing here to see if someone has any idea, it seems I'm not able to understand the reason.
I setup Google Pay on my OnePlus 5 and it was working perfectly, up until some days ago. Now when I put the phone close to the POS, nothing happens, even if I open the Google Pay app before placing the phone near the terminal.
I performed a factory reset of the phone, after that, Google Pay started working again, but then, after a few hours, it just stopped with the same exact behavior, meanwhile I had restored the backup of most of my apps.
I again performed a factory reset, Google Pay started working properly, then slowly started re-installing and re-configuring my apps, constantly testing if Google Pay was working (luckily I found out how to "test" if Google Pay is working without having to buy something*), everything was working properly, but then, apparently without reason, Google Pay stopped working again in the exact same way.
I pinpointed the problem down to Google Pay and not generically to NFC, because Android Beam and other NFC apps are working perfectly. I also tried an app from Visa that emulates a credit card for test purposes (Visa Mobile CDET), this app replaces Google Pay as Tap&Pay provider and when I test the NFC payment with that app set as default, it works, the test card is sent over to the receiving terminal. As soon as I change the default Tap&Pay to Google Pay, nothing happens anymore.
Some additional info: my OnePlus 5 has never been rooted, it is up to date with the latest firmware (OxygenOS 9.0.6). Google Pay is version: 2.90.250604638
Is anyone experiencing the same issue?
thanks a lot!
moebius83 said:
Hi all!
I'm writing here to see if someone has any idea, it seems I'm not able to understand the reason.
I setup Google Pay on my OnePlus 5 and it was working perfectly, up until some days ago. Now when I put the phone close to the POS, nothing happens, even if I open the Google Pay app before placing the phone near the terminal.
I performed a factory reset of the phone, after that, Google Pay started working again, but then, after a few hours, it just stopped with the same exact behavior, meanwhile I had restored the backup of most of my apps.
I again performed a factory reset, Google Pay started working properly, then slowly started re-installing and re-configuring my apps, constantly testing if Google Pay was working (luckily I found out how to "test" if Google Pay is working without having to buy something*), everything was working properly, but then, apparently without reason, Google Pay stopped working again in the exact same way.
I pinpointed the problem down to Google Pay and not generically to NFC, because Android Beam and other NFC apps are working perfectly. I also tried an app from Visa that emulates a credit card for test purposes (Visa Mobile CDET), this app replaces Google Pay as Tap&Pay provider and when I test the NFC payment with that app set as default, it works, the test card is sent over to the receiving terminal. As soon as I change the default Tap&Pay to Google Pay, nothing happens anymore.
Some additional info: my OnePlus 5 has never been rooted, it is up to date with the latest firmware (OxygenOS 9.0.6). Google Pay is version: 2.90.250604638
Is anyone experiencing the same issue?
thanks a lot!
Click to expand...
Click to collapse
Not directly, but maybe you get some ideas of those discussions for magisk/Google pay
https://forum.xda-developers.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post79016060
https://forum.xda-developers.com/on...nos-beta-1-android-oreo-t3710003/post79030908
spot on! thanks!
I never thought about Play Services, but that's the issue indeed.
The version I had installed was:
17.4.55 (100400-248795830)
May 21, 2019
arm64-v8a + armeabi-v7a
Android 9.0+
nodpi
Click to expand...
Click to collapse
I reverted to the previous one I found on apkmirror:
17.1.94 (100400-248977010)
May 21, 2019
arm64-v8a + armeabi-v7a
Android 9.0+
nodpi
Click to expand...
Click to collapse
and now Google Pay is working again.
I guess this means there was a bug introduced on the latest version or something like that, it's difficult to say without a changelog
At least this explains the random behavior, Play Services libraries are probably updated in background automatically.
thanks for the hint! Now I have to make sure Play Services libraries won't update automatically and I probably need to monitor new releases as I don't want to stick with an old version forever.
Opened a ticket on the google issue tracker: https://issuetracker.google.com/issues/135132389 please "star" it and add your comments, we need to understand if this is just a OnePlus issue.
Opened a ticket on OnePlus forum: https://forums.oneplus.com/threads/...-5-after-google-play-services-update.1053102/
Possible workaround, however not very straightforward and comfortable, but could be useful to troubleshoot:
- Install Visa Mobile CDET app: https://play.google.com/store/apps/details?id=com.visa.app.cdet&hl=en
- set it as default Tap&Pay app
- as "Use default" option, select "Except when another payment app is open"
- open Google Pay app and keep it in foreground
- pay with Google Pay
moebius83 said:
Opened a ticket on the google issue tracker: https://issuetracker.google.com/issues/135132389 please "star" it and add your comments, we need to understand if this is just a OnePlus issue.
Opened a ticket on OnePlus forum: https://forums.oneplus.com/threads/...-5-after-google-play-services-update.1053102/
Possible workaround, however not very straightforward and comfortable, but could be useful to troubleshoot:
- Install Visa Mobile CDET app: https://play.google.com/store/apps/details?id=com.visa.app.cdet&hl=en
- set it as default Tap&Pay app
- as "Use default" option, select "Except when another payment app is open"
- open Google Pay app and keep it in foreground
- pay with Google Pay
Click to expand...
Click to collapse
what is Visa Mobile CDET for? i've read the description on google play but i don't understand what it is supposed to do...
alessandro_xda said:
what is Visa Mobile CDET for? i've read the description on google play but i don't understand what it is supposed to do...
Click to expand...
Click to collapse
From what I understand, it emulates different types/technologies of contactless cards, so merchants can be sure their POSs are compatible with that type/technology of cards.
It should be "safe".
I tried the workaround, and I can confirm it works.
Now we just have to organize a meeting in Bologna, the issue seems to be here
andreacos92 said:
From what I understand, it emulates different types/technologies of contactless cards, so merchants can be sure their POSs are compatible with that type/technology of cards.
It should be "safe".
I tried the workaround, and I can confirm it works.
Now we just have to organize a meeting in Bologna, the issue seems to be here
Click to expand...
Click to collapse
Exactly, the app itself is not useful to us, but it lets you change Tap&Pay default to another app that is not Google Pay and this seems to be unlocking Google Pay for some reason.
I'm really starting to think that the issue is only in Bologna
moebius83 said:
Exactly, the app itself is not useful to us, but it lets you change Tap&Pay default to another app that is not Google Pay and this seems to be unlocking Google Pay for some reason.
I'm really starting to think that the issue is only in Bologna
Click to expand...
Click to collapse
maybe.
I've OOS 9.0.5, with franco kernel and latest magisk, and I've tried Gpay this week and it still work. /canada , visa.
oVeRdOsE. said:
maybe.
I've OOS 9.0.5, with franco kernel and latest magisk, and I've tried Gpay this week and it still work. /canada , visa.
Click to expand...
Click to collapse
Which Google Play Services and Google Pay version? Thanks
Hello everyone. Finally I found someone else with this problem! Since may/june 2019 I'm having this strange issue of Google Pay not working anymore. I've been in contact with Google and OnePlus, they reflashed OxygenOS but nothing solved the problem. Google Play Services is now updated to the version 19.4.20, but Google Pay and other NFC apps still don't work. The strange thing is that some NFC apps work properly, other do not work at all... Just like Google Pay. In the meantime, did someone found a stable solution? Thank you all.
Hello Frank!
the only workaround is the one described above, unfortunately, no solution is offered, but it seems it's some kind of compatibility issue with other nfc apps.
for example, andreacos92 realized that after a factory reset, Google pay works properly, but the moment he installed Muver (an Italian nfc app to use mobile bus tickets) and after the first reboot, Google pay stops working, even uninstall ing Muver will leave Google pay broken, the only solution is another factory reset.
any chance you're also using that app? Or perhaps another one using nfc?
For quite some time now I'm searching for a solution for the following issue, for which so far anything I tried didn't solve it. Hoping someone here has a suggestion on how to resolve it.
Several times per day an unknown app sends an url to open in the Samsung Browser. Each time it's a different website, so blocking the site or domain doesn't work.
I cleaned cache/date, blocked background data for apps, reset everything, used dozens of malware/android security apps - none of these apps found anything suspicious - running AdGuard, tried all Samsung Browser Ad blocker, uninstalled app by app to find the causing one, but nothing solved the issue so far.
What are your thoughts?
Thank you.
TGSKK said:
For quite some time now I'm searching for a solution for the following issue, for which so far anything I tried didn't solve it. Hoping someone here has a suggestion on how to resolve it.
Several times per day an unknown app sends an url to open in the Samsung Browser. Each time it's a different website, so blocking the site or domain doesn't work.
I cleaned cache/date, blocked background data for apps, reset everything, used dozens of malware/android security apps - none of these apps found anything suspicious - running AdGuard, tried all Samsung Browser Ad blocker, uninstalled app by app to find the causing one, but nothing solved the issue so far.
What are your thoughts?
Thank you.
Click to expand...
Click to collapse
Look for an app named "Mobile Installer" or "Mobile Services Manager". They install apps in the background and cause system wide 'pop-up' ads. You can use PD MDM to disable it if you cant through settings.
Sent from my SM-G975U using XDA Labs
jwarrior319 said:
Look for an app named "Mobile Installer" or "Mobile Services Manager". They install apps in the background and cause system wide 'pop-up' ads. You can use PD MDM to disable it if you cant through settings.
Sent from my SM-G975U using XDA Labs
Click to expand...
Click to collapse
Thank you.
I looked in PD MDM for such an app but don't have one with or similar to the names you mentioned.
I noticed that the package on your screenshot is a Sprint related app. I'm sorry I didn't mention before, but I have an unlocked device on T-Mobile, without any carrier specific apps.
TGSKK said:
Thank you.
I looked in PD MDM for such an app but don't have one with or similar to the names you mentioned.
I noticed that the package on your screenshot is a Sprint related app. I'm sorry I didn't mention before, but I have an unlocked device on T-Mobile, without any carrier specific apps.
Click to expand...
Click to collapse
The unlocked firmware wouldn't have either app anyway. That does make me wonder what's causing the issues. The apps i mentioned are installed by carriers on most android devices. They make money from the ads and when someone opens an app it auto installed. I first discovered it on my S5 with stock firmware. At that time data plans were still limited and it would be downloading 100+mb apps on data even with background data disabled.
Sent from my SM-G975U using XDA Labs
Factory reset.
You must a naughty individual surfing for porn..you should use your friends or your wife's phone to surf for porn. Thats what i do