There's nothing there to link them. If I adjust the ring volume, the notification doesn't change with it. I find it really annoying.
[ROM] BarePapA - ZVA
- Thread starter engine95
- Start date
-
- Tags
- development
That error is because Android Pay will not allow you to add a card on a Rooted device. There is a workaround however! Go to SuperSU > Settings > and uncheck "Enable Superuser". Now go ahead and add all the cards you need to add on Android Pay. Now go back and check "Enable Superuser" and Android Pay should work just fine. For whatever reason Google will not allow a rooted device to add cards, but they can use the app. If you use this workaround it fools the phone into thinking it is no longer rooted and will allow you to add the cards!
Be glad that you can do that. They won't enable Pay if your bootloader is unlocked (not Bumped, but genuinely unlocked)
I had tried that (and a method using an xposed module called Rootcloak) before i made my post and it 100% did not work
I miss understood what you were wanting, but just tried Linked Volume Control at playstore and that links them together with this app. Hope that helps. It was made from Samsung device but just tested and it works
Thanks, I downloaded "simple volume" and that works well too.
Worked for me, just installed. Didn't hid root, but I do have mount namespace separation unchecked in superSU. Also xposed installed.
Weird... I just tried unchecking that on mine and it still didn't work.
I even went so far as to roll back google play services to stock, uninstall Android Pay, uncheck Namespace and enable superuser, then restart... from there I installed the updated google place services, then installed Android pay, went thru the setup and got the same result.
There has to be another variable blocking me (and others) if you were able to do it successfully...
In the mean time I just uninstalled android pay and new wallet, rolled back Play services to stock, installed v7.8.99 and Google Wallet v9.0-R206-v27 (last version before android pay) so I can have everything working till a universal fix comes about
Yeah I can't get pay to work either. Tried everything people have said. Someone will figure it out!
And that "someone" just happens to be ME!
So, I got a wild hair up my butt this morning and said "I wonder if somehow xposed has anything to do with this problem" despite the fact that a friend of mine is running the stock OS that he has ONLY rooted and installed xposed on, and he could install Android Pay without issue.
Anyways, I decided to give it a try...
I went to the Xposed for Lollipop thread and got the xposed-uninstaller-20150831-arm.zip.
Put that on the root of your internal SD.
I uninstalled the Xposed app itself (Settings<Apps<all) just in case, though Im not sure if you even need to. I just did so that I know I was 100% "Xposed-free".
Next I uninstalled Android Pay, so that I could start with a fresh install when going thru the setup, so no past gremlins could possibly be hanging around.
I also went in SuperSU and unchecked the box for 'Enable Superuser' and 'Mount Namespace Seperation'...again, not sure if this is needed, but It was known to cause issues with others so I figured if I'm going thru the trouble to try this one last thing, I may as well uncheck/disable/etc ALL THE THINGS lol!
After that, reboot to recovery, flash the xposed-uninstaller-20150831-arm.zip and reboot.. The update/uninstall will take a bit, so let it do its thing
Now, once you're booted, install Android Pay and go thru the setup.... aaaaaaaaaand IT WORKS!
I then went thru THESE steps to reinstall Xposed and everything still works. Since I didn't uninstall tweaksbox all of my settings and everything were still there so as soon as I rebooted after fully installing Xposed everything was back the way I had it before, and also android pay still open and seems to run as it should....
I haven't actually attempted to tap and pay yet, since I'm at work, but I see no real reason why it won't work.
**UPDATE**
So, when I went thru the setup, since I used the Old Google Wallet previous, it still had my cards stored... all I had to do was put in the security codes from the back of the cards and all was well.
Well, Yesterday I got a replacement debit card to replace one of the cards already on my Google wallet (card was expiring soon). So, I removed the old card, and then went thru the steps to add the new card and...it says "This card can't be use. Your bank doesn't support Android Pay yet"
Ummmmmmmm.... how can that be true?
I had two debit cards on my Google Wallet....both TCF Bank. I removed one TCF card, and tried to replace it with a new TCF card for the SAME account as the one I just deleted...and it says my bank doesn't support Android Pay lol...
Not sure if the Card the that is still on there/it let me add will maybe not work when I actually attempt to use it to pay (since it's supposedly "Not supported" lol) but yeah...
Sadly the card that is still on Android pay is the one to a secondary account that I don't generally use, and the one it won't let me add is my everyday use account... so, even though I now have working Android Pay, it's really of no use to me lmao!
I'm going to leave it installed just so I can go make a test pay to confirm that it's working and report back, but then I think I'm going to end up rolling back my Android Services again and reinstall the Old Wallet app so I can still use both my cards till whenever my bank gets "officially added" haha
Last edited:
thats the method i used to get it to work on Stock_ZVA_L_Odexed when android pay was first released last week and can confirm it works on barepapa as well...
The old Google Wallet worked differently than Android Pay does.
When you paid with Google Wallet, you paid with a virtual MasterCard number that Google assigned to you, so Google/MasterCard handled the transaction with the vendor, and then dealt with your bank. So your bank knew nothing about the vendor transaction or what Google Wallet was doing, only about the MasterCard transaction.
When you pay with Android Pay, you're paying directly with the credit/debit card you added, so your bank handles the transaction with the vendor. It knows all about Android Pay, and needs to support it.
That's why the same card can work in Google Wallet but not in Android Pay, if your bank doesn't support Android Pay.
See thats just it. the same two cards DID work in Google Wallet and Android Pay.
The issue came when I needed to replace one of those two cards...
It was like this:
card#1234 is for account A and card#5678 was for account B. Both were added to and used in Google Wallet.
When I finally got Android Pay working, both cards were able to be added (by confirming the security codes on the back of the cards) no problem at all.
Then I received card#7654 for account A (this replaces the other card since it was expiring soon) so I delete the original, completely added and working card for account A, then attempt to replace it with the new card and it tells me my bank doesn't support Android Pay.
How can this be when my two cards/accounts from that very same bank 100% worked in both Google Wallet AND Android Pay?
I read elsewhere something to the effect of "any cards that were added to Wallet prior to the update to Pay are "grandfathered in" and will continue to work...so, in an attempt to make things work I rolled everything back and installed the OG Wallet app, added my new card#7654 in the app, it adds absolutely fine. For good measure I even went out and made a purchase using that card in Wallet. I am waiting for that transaction to be marked 'complete' in the transaction history before I then install the updated Play Services and install Android Pay and go thru the setup again.
I am hoping that since the card was added via Wallet and used in Wallet that it will then meet the criteria to be "grandfathered in" like my other two cards were...though, I suspect that the deal is that it is any card that was added to Wallet before Android Pay was RELEASED falls into that Grandfathered designation.....
We'll see!
The cards that were added in GW and that now appear in AP are still using the virtual MasterCard from the GW days. So your bank still knows nothing about the vendor transactions, and that's why it still works (and what they mean by grandfathered in). They're not going directly through your bank like they would if you delete them and add them in AP as new cards.
I suspect that too... And if that's the case I could care less.
I just need to be able to use the card that is for my "Account A" that I described above since it is my primary account otherwise Android Pay is useless to me.
If they've got to still do the virtual Mastercard on the back end, whoopty-doo...
But if this doesn't work, then until my bank plays nice, I'll just continue rockin the rolled back old school Google Wallet app in the mean time...
rejoice my friends, for we are saved. The Great El Gee is merciful, and has delivered us from our long national nightmare of remote code execution via an appropriately badass-named protocol, 'stagefright'
Now to remember how to get this **** off my phone and keep it off. Again.
I haven't even checked the other threads so I dont know if this has been done, but I went ahead and pulled the OTA update.zip out of /cache and hosted it on medifire in case it should be useful to engine or others: LS990 Stagefright OTA update.zip
Now to remember how to get this **** off my phone and keep it off. Again.
I haven't even checked the other threads so I dont know if this has been done, but I went ahead and pulled the OTA update.zip out of /cache and hosted it on medifire in case it should be useful to engine or others: LS990 Stagefright OTA update.zip
Last edited:
So is this a new update for our phones?rejoice my friends, for we are saved. The Great El Gee is merciful, and has delivered us from our long national nightmare of remote code execution via an appropriately badass-named protocol, 'stagefright'
Now to remember how to get this **** off my phone and keep it off. Again.
I haven't even checked the other threads so I dont know if this has been done, but I went ahead and pulled the OTA update.zip out of /cache and hosted it on medifire in case it should be useful to engine or others: LS990 Stagefright OTA update.zip
It must be. But don't install it! You'll risk losing root/unlock!
To be on the safe side, we need to wait for @autoprime to have a look at it. Or come up with either the tot/img files.
To be on the safe side, we need to wait for @autoprime to have a look at it. Or come up with either the tot/img files.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone