Anyone have any ideas as to how we could get Wallet working? I installed a few different versions and none of them seemed to work. I tried the modded version that was released for the GNEX and got an insecure element error (but not as an fc) and also tried the latest version I have on my GNEX but got another error (sshot) I would be happy to try out other ideas if anyone has any...
(Rooted) Modify the build props to a Sprint GS3?
This disappoints me, Google Wallet was something I was really looking forward to using. There's a Walgreens with NFC payment machines that I usually ride my bike to for quick things like milk, bread, etc. I was looking forward to leaving my wallet at home and just biking with the phone...I hope that we get that functionality sometime soon.
tlogank said:
This disappoints me, Google Wallet was something I was really looking forward to using. There's a Walgreens with NFC payment machines that I usually ride my bike to for quick things like milk, bread, etc. I was looking forward to leaving my wallet at home and just biking with the phone...I hope that we get that functionality sometime soon.
Click to expand...
Click to collapse
It's unlikely. Verizon Wireless has a competing product. They would much rather you use that than Google Wallet. There are a lot of NFC payment apps out there, whether they're Google/Apple side, carrier side, or bank side. They all want to become banks. I doubt Google Wallet will work on this device without some serious trickery.
When is ISIS coming anyway? These carriers are surely being assholes not even giving people a way to use NFC payments while ISIS jerks off. With all of them backing ISIS, I'm surprised it hasn't launched outside their test zone yet.
Google Wallet isn't competing if they don't even have their product commercially available yet.
Hilbe said:
(Rooted) Modify the build props to a Sprint GS3?
Click to expand...
Click to collapse
How do you that? Is it as simple as replacing the model to the Sprint's one?
Check here for all the research I've already done.
HTML:
http://forum.xda-developers.com/showthread.php?p=28432068
Are there any working alternative services to Google Wallet on Verizon at the moment?
I am pretty sure there is nothing else, the fact that verizon is blocking the only option really pi$$es me off, I will NEVER use isis
grhomes said:
Anyone have any ideas as to how we could get Wallet working? I installed a few different versions and none of them seemed to work. I tried the modded version that was released for the GNEX and got an insecure element error (but not as an fc) and also tried the latest version I have on my GNEX but got another error (sshot) I would be happy to try out other ideas if anyone has any...
Click to expand...
Click to collapse
Hate to break it to ya, but if you are getting the secure element error then you have (as of right now) permanently bricked your ability to use wallet and possibly other nfc payment options in the future. Ask me how I know
ISIS is not out yet, right? So there is no payment option for this yet?
Sent from my SCH-I535 using xda premium
cttwarnock said:
Hate to break it to ya, but if you are getting the secure element error then you have (as of right now) permanently bricked your ability to use wallet and possibly other nfc payment options in the future. Ask me how I know
Click to expand...
Click to collapse
I thought somebody just came up with an ADB shell call something along the line of reset broadcast something that could potentially fix the issue of bricked SE's?
Anybody know if anyone is planning on developing a Wallet app to work on Verizon GSIII. Isis is going to be terrible, because it won't work wherever a PayPass terminal is, only at select retailers, but thousands of retailers already use PayPass terminals, so I was hoping for Wallet.
Sent from my SCH-I535 using xda app-developers app
I want this bad. I will stalking this thread for updates
Well that was the first apk I tried, uninstalled and then got the sshot that was posted....I hope thats not the case but seeing as how I got a different error I sincerely doubt it...working on a few evo 4g wallet workarounds atm...
jackdubl said:
ISIS is not out yet, right? So there is no payment option for this yet?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Isis is supposed to hit the SLC area any day now, and some other select areas for testing. Isis is close, and looks like it's going to be awefully similar to Google Wallet. You can link it with supported brands of credit card or use their rechargeable card just like your google wallet account. Way to not innovate. I wonder if Google could pull and Apple and sue...?
http://www.paywithisis.com/get-isis.xhtml
konman2k4 said:
I thought somebody just came up with an ADB shell call something along the line of reset broadcast something that could potentially fix the issue of bricked SE's?
Click to expand...
Click to collapse
Can you link that? I cant find it anywhere. That would be so helpful!
I'm not an expert on how Android does credential storage, but I poked around a bit with this version of 1.1-R67-v12, which is patched to avoid region, device, and carrier restrictions. When pushed to /system/app this version launches fine, but when I attempt to link my account I get this:
I checked out the device logs, and I believe this is because our /etc/nfcee_access.xml does not contain the requisite keys to run Wallet:
Code:
NfcServiceSecurityException: java.lang.SecurityException: /etc/nfcee_access.xml denies NFCEE access to com.google.android.apps.walletnfcrel
07-11 20:29:25.678 E/InitializerTaskManagerImpl(1853): java.util.concurrent.ExecutionException: com.google.android.apps.wallet.secureelement.NfcServiceSecurityException: java.lang.SecurityException: /etc/nfcee_access.xml denies NFCEE access to com.google.android.apps.walletnfcrel
As I understand it, this is something that has to be built into the system at compile-time, but I could be wrong. With the correct keys I believe the app will run fine - but as others have pointed out, most of the development effort is (rightly) going into bootloader circumvention at the moment. I have no doubt we'll get access to Wallet in the near future - probably coinciding with the release of CM9 or some other custom ROM.
Expanded logcat here for the curious.
This isn't going to help you verizon folks, but I just got this working on tmobile (havent tested it, but it is installed, no errors, card added)
I'm betting it'll work on att or any other carrier that has a cm9 build.
First thing i did was a backup, then i wiped and installed cm9
then i used the apk and followed the instructions found here and performed the build.prop tweaks found here
Now I'm good to go :good:
dcmtnbkr said:
This isn't going to help you verizon folks, but I just got this working on tmobile (havent tested it, but it is installed, no errors, card added)
I'm betting it'll work on att or any other carrier that has a cm9 build.
First thing i did was a backup, then i wiped and installed cm9
then i used the apk and followed the instructions found here and performed the build.prop tweaks found here
Now I'm good to go :good:
Click to expand...
Click to collapse
Did you have all 3 lines in the build.prop? I can only see 2 of them. AT&T GS3.
Related
Google Wallet - Everything you need to know before you flash or root!
DISCLAIMER: I DO NOT TAKE ANY RESPONSIBILITY FOR ANY DAMAGE THAT OCCURS TO YOUR PHONE. THIS IS A COLLECTION OF INFORMATION I FOUND WHILE ROOTING AND FLASHING ROMS. I ONLY ORGANIZED IT HERE TO MAKE IT EASIER FOR PEOPLE TO FIND.
Don't forget to thank people who made the ROMs, Root Methods, etc. They put in a lot of work and take a lot of time helping people. All it takes is a click of a button. One for me too! It's a lot of work trying to keep everything updated. =P
This will and always will be a work in progress. If you feel something should be added, clarified, or corrected feel free to PM me. I'm not perfect and I can't read everything so any and all help is appreciated. (Yes of course I will credit you. Just no plagiarism!)
-----------------------------------------------------------------------------
What is Google Wallet?
http://www.google.com/wallet/what-is-google-wallet.html
The new update has simplified the process greatly. Now all cards can be added and all transactions are saved to the cloud. Very minimal information is saved on the device. There is also a very very very slim chance at breaking your secure element.
What do I need to know before I start rooting or flashing ROMs?
While there is much debate over whether or not to Reset Google Wallet before wiping the device, you should do it just in case. There needs to be more testing done to see if the Secure Element will be broken if you don't.
To Reset Google Wallet do the following:
1) Open Google Wallet
2) Enter your pin
3) Tap your Menu Button
4) Tap Settings
5) Tap "Reset Google Wallet"
You should also write down your Google Prepaid Card User ID as well prior to resetting just incase. This will help Google find your money incase your ID changes. You only have to do this once. So far the USER ID has not changed for me ever. This change happens when you physically change phones. Also make sure you know the balance on the card.
Write down your Google Prepaid Card User ID.
1) Open Google Wallet
2) Enter your pin
3) Tap "Payment cards"
4) Tap "Google Prepaid Card"
5) Wait for your User ID to load and then tap "Show ID" to see your entire ID number. Write this down BEFORE FLASHING OR CLEARING DATA.
Once you do this you are good to go and flash a custom ROM. You can wipe data, cache, dalvik without an issue.
After you have set up your new ROM, download and install the latest Google Wallet in the Play Store.
Once you login, Google Wallet will now automatically pull from the cloud any credit cards on file. All you have to do is set them up by tapping them. Some will automatically setup, others will require you to enter in all the card and billing details.
Google Prepaid Cards you have to tap to add. It should pull all the funds and the same user ID as before. If the funds do not pull up, make sure you have your User ID from above, and call Money Network. Their number is (855) 896-0693.
As I don't have every single credit card type, please post in this thread if you run into any issues. I'll update the OP
-----------------------------------------------------------------------
ROOTED USERS:
If you are rooted but stock and you have never used the Google Wallet application, there are a few things you need to know:
#1 - You will always get an unsupported error at the top of your Google Wallet application. Do not worry. Google Wallet will still work as long as you didn't break your secure element. If you can add a Google Prepaid Card and add funds, then you can use it.
#2 - If you try to call in for support, Citi Mastercard will not help you since you are rooted. Google Wallet and Money Network will give you very limited support if you are rooted.
#3- Some users are finding success restoring their backups of Google Wallet to fix broken secure elements. I will need more confirmation but if it is broken, what do you have to lose.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Common Questions + Issues
How to get it up and running on actual unsupported devices:
You will have to edit your build.prop to make Google Wallet think your phone is one of the ones supported.
Here are instructions. This is not for everyone. Sprint users won't have to do all this.
http://forum.xda-developers.com/showthread.php?t=1769083
How do I use Google Wallet to purchase items?
1) You do not need to have the app open but the phone must be turned on. (There are some ROMs that turn NFC on without the screen being on, but you will still need to put in your PIN so just turn the screen on)
2) Let the cashier know you are paying credit or press credit on the credit card terminal.
3) Place the BACK of the phone on the sensor of the card terminal. You can put it on the terminal or place it near but it has to be within an inch or two.
4) Remove the device and enter your pin.
5) Follow directions on the screen till your transaction is complete.
6) When in doubt, ask the cashier if it went through. Most will be amazed and think its cool and spend time with you to get it to work. lol
I think my secure element is broke. How do I tell? How do I fix it?
Check out this explanation w/screenshots. Great work Hobadee!
http://forum.xda-developers.com/showpost.php?p=35156196&postcount=93
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I hope this helped you. If it has, please click thanks!
Thanks to Racer of All and Rev3ge07 for their contributions on the Secure Element. Thanks to ogdobber for the build.prop tutorial. Thanks to Hobadee for the secure element soft brick fix explanation.
[/strike]
Cool write-up.
and can you clarify in the OP, that if someone HASN'T used google wallet, or "enabled" any cards on a phone, they don't have to mess with any of this, right? can they flash a new rom normally?
okay... and another hypothetical situation: what if someone originally HAD google wallet, did everything as stated in the OP, but after they flashed a new rom, they didn't bother with google wallet, so the app was never installed. does that person have to do anything before installing a FUTURE rom? or what?
Lieu10ant said:
Cool write-up.
and can you clarify in the OP, that if someone HASN'T used google wallet, or "enabled" any cards on a phone, they don't have to mess with any of this, right? can they flash a new rom normally?
okay... and another hypothetical situation: what if someone originally HAD google wallet, did everything as stated in the OP, but after they flashed a new rom, they didn't bother with google wallet, so the app was never installed. does that person have to do anything before installing a FUTURE rom? or what?
Click to expand...
Click to collapse
I'll update the OP for that once I get to work.
Sent from my SPH-L710 using Tapatalk 2
the first post makes it sound like this only applies to citibank master cards, but I'm assuming this affects all credit cards you load into google wallet?
First, if someone (ie me) only has the free $10 dollars from google wallet, then you only need to do the part for the google prepaid card?
And, do you know if anything needs to be done about any of the gift cards that you can add in. I have not done any yet but I do plan to at some point.
Thanks and great job. The instructions are pretty straightforward which is always important when you're dealing with money related things.
sweetness. works perfect on my verizon s3. just added my google card about 15 minutes ago, 10 bucks showed up and just tried it at 7-11. worked perfect. thanks a million OP
wow thanx
wow thanx for the tutorial
inline6power said:
sweetness. works perfect on my verizon s3. just added my google card about 15 minutes ago, 10 bucks showed up and just tried it at 7-11. worked perfect. thanks a million OP
Click to expand...
Click to collapse
I still get the "unsupported device" error on my Verizon S3. Can you tell me which Wallet app you are using? Is it the one from the Play store or a modded one? I'm on the stock rooted rom btw.
Thanks.
skiddingus said:
I still get the "unsupported device" error on my Verizon S3. Can you tell me which Wallet app you are using? Is it the one from the Play store or a modded one? I'm on the stock rooted rom btw.
Thanks.
Click to expand...
Click to collapse
Go Here
http://forum.xda-developers.com/showthread.php?t=1769083
inline6power said:
sweetness. works perfect on my verizon s3. just added my google card about 15 minutes ago, 10 bucks showed up and just tried it at 7-11. worked perfect. thanks a million OP
Click to expand...
Click to collapse
How did you get wallet to work on verizon galaxy s3 at the store? I got it setup but it won't work in store when I try to use it.
Sent from my SCH-I535 using Tapatalk 2
I get the unsupported device message on my sprint gs3 and I didn't open or do anything to google wallet before flashing blazers rom
Did I void Google Wallet on my phone indefinitely if it added my Gmail account, but I never added a prepaid card yet. Then flashed a new from...??? I set up a pin but never added a card...
Sent from my htc_SIII using xda premium
antispiral said:
How did you get wallet to work on verizon galaxy s3 at the store? I got it setup but it won't work in store when I try to use it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Have no clue I just follow ed the op instructions and our worked for me
sent from my galaxy s3
Can you wallet uninstall using rom toolbox / titantium backup before flashing rom and after flashing new rom re-install using rom toolbox/titantium backup
So no one has found out what files on the rom need to be backed up to keep google wallet from breaking? That seems like a lot to go through everytime the rom gets upgraded.
Thank you to share!
Thank you to share!：好：
many thanks:good:
Great guide! Thank you so much!
Thank you:thumbup:
Gesendet von meinem GT-N7000 mit Tapatalk 2
Thanks
sekigah84 said:
I'll update the OP for that once I get to work.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Thank you very much:good:
http://api.viglink.com/api/click?format=go&key=8600f7534c0088ea32780070d5258fc2&loc=http%3A%2F%2Frootzwiki.com%2Ftopic%2F31535-new-google-wallet-uses-all-cards%2F&v=1&libid=1343856431352&out=http%3A%2F%2Fgooglecommerce.blogspot.com%2F2012%2F08%2Fuse-any-credit-or-debit-card-with.html%3Fm%3D1&ref=http%3A%2F%2Frootzwiki.com%2Fforum%2F507-galaxy-s-iii%2F&title=New%20Google%20Wallet%20uses%20all%20cards%20-%20Galaxy%20S%20III%20-%20RootzWiki&txt=http%3A%2F%2Fgooglecommerc...d-with.html%3Fm%3D1&jsonp=vglnk_jsonp_13438564324821
DESCRIPTION
http://api.viglink.com/api/click?fo....tt/L5RanT6j&jsonp=vglnk_jsonp_13438564998952
DOWNLOAD LINK
Come on man, the answer to your question is being discussed 6 posts below yours....
http://forum.xda-developers.com/showthread.php?t=1807608
Actually that method don't work on NEW google wallet version.. Just tried it a second ago..
sn0warmy said:
Come on man, the answer to your question is being discussed 6 posts below yours....
http://forum.xda-developers.com/showthread.php?t=1807608
Click to expand...
Click to collapse
Im asking for a WORKING method... if was easy as me reading 6 posts down and it WORKING, i never would have made this thread.... that thread was regarding the older wallet fix... not for the New google wallet thats available....
joemagistro said:
Im asking for a WORKING method... if was easy as me reading 6 posts down and it WORKING, i never would have made this thread.... that thread was regarding the older wallet fix... not for the New google wallet thats available....
Click to expand...
Click to collapse
Well now I feel like a **** so I will begin my search. :cyclops:
haha np... i doo search threads you know.. and when i cant find the answer... i post threads like these...
i even tried renaming my build.prop to 2 other sprint phones that wallet is available on..... still gives me a UNSUPPORTED DEVICE OR NETWORK error and closes on me.. soo theres gotta be something else to it other then renaming the build
ive been waiting for this update for awhile where google wallet will let me use any credit/debit card instead of just keep reloading my prepaid card... theres gotta be a way to get this working
Here is how I got it working:
1: Change build.prop lines to
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
2: Flash the Tmobile wallet zip found in the other google wallet guide.
http://forum.xda-developers.com/attachment.php?attachmentid=1194288&d=1342133553
3: update wallet from the play store and open it.
4: set up and everything should work!
NOTE: Do not change build.prop back it will break wallet!!!!
EDIT: seems to be working fine after changing the build.prop back but I haven't made a purchase yet.
jellydroid13 said:
Here is how I got it working:
1: Change build.prop lines to
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
2: Flash the Tmobile wallet zip found in the other google wallet guide.
http://forum.xda-developers.com/attachment.php?attachmentid=1194288&d=1342133553
3: update wallet from the play store and open it.
4: set up and everything should work!
NOTE: Do not change build.prop back it will break wallet!!!!
Click to expand...
Click to collapse
THANK YOU!! soo basically its either keep s-voice or keep wallet... i cant have both since im changing the build.prop name.. correct?
joemagistro said:
THANK YOU!! soo basically its either keep s-voice or keep wallet... i cant have both since im changing the build.prop name.. correct?
Click to expand...
Click to collapse
Is there anything else that gets effected by changing those three?
jellydroid13 said:
Here is how I got it working:
1: Change build.prop lines to
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
2: Flash the Tmobile wallet zip found in the other google wallet guide.
http://forum.xda-developers.com/attachment.php?attachmentid=1194288&d=1342133553
3: update wallet from the play store and open it.
4: set up and everything should work!
NOTE: Do not change build.prop back it will break wallet!!!!
Click to expand...
Click to collapse
worked like a charm. I didn't have to update from Play Store. As soon as i opened it, it just prompted me to verify and confirm my debit card info. Awesome! Thanks!
I can finally use my debit card to pay with my phone :highfive:
babymatteo said:
worked like a charm. I didn't have to update from Play Store. As soon as i opened it, it just prompted me to verify and confirm my debit card info. Awesome! Thanks!
I can finally use my debit card to pay with my phone :highfive:
Click to expand...
Click to collapse
it was such a pain to keep reloading my card... thats awesome that its directly linked to my bank card!!
i THINK the only thing thats effected with changing the build is S-voice not working.... right??
Nevermind...
joemagistro said:
it was such a pain to keep reloading my card... thats awesome that its directly linked to my bank card!!
i THINK the only thing thats effected with changing the build is S-voice not working.... right??
Click to expand...
Click to collapse
For me, running CM9 Nightlies, anytime i flash the wallet "fixes" it removes the NFC option completely for me. So, i can't even finish the activation... testing this method out, will report back...
EDIT: Ok, so using the "Tmobile Fix" didn't work for me, like i expected. BUT what did work for me, is, change the build.prop info like previously stated (Google Nexus, yakju, maguro) reboot, then update from marketplace. And it allowed me to add my debit card. Although it says "Unsupported device" up at the top, but it still let me open it and add my bank card. Will find out when i try to buy something...
So why would wallet not support all devices now that we can add our own cards?! Is this something that will officially change as more models will be added to list of supported devices? I really don't want to edit the build.prop as i am sure a few other things will break.
Sent from my SGH-T999
first thank you for teach us how to set up google wallet
I follow your steps set up everything looks verything fine but in the final said on the screen see the picture below
also I stuck at adding card.......any idea how to fix it?
rakeshchn said:
So why would wallet not support all devices now that we can add our own cards?! Is this something that will officially change as more models will be added to list of supported devices? I really don't want to edit the build.prop as i am sure a few other things will break.
Sent from my SGH-T999
Click to expand...
Click to collapse
I read the "Unsupported device" message, and it was basically saying, that because we're using rooted devices, and unsupported, our credit card information may not be as secure as a fully functioning proper device. I think....
So I was able to get the updated Wallet working using the Galaxy Nexus build.prop settings.
However, I have yet to make a transaction, so I can't say that it "fully" works.
Also, I'm running CM9 and not stock, so I'm not sure if that will make a difference.
EDIT: I followed the instructions using this thread and following the instructions in the OP.
InversedTech said:
So I was able to get the updated Wallet working using the Galaxy Nexus build.prop settings.
However, I have yet to make a transaction, so I can't say that it "fully" works.
Also, I'm running CM9 and not stock, so I'm not sure if that will make a difference.
Click to expand...
Click to collapse
Ya same. And as to changing the build.prop back I have not tried but I heard from others it doesn't work.
EDIT: seems to be working fine after changing the build.prop back but I haven't made a purchase yet.
Susasama said:
For me, running CM9 Nightlies, anytime i flash the wallet "fixes" it removes the NFC option completely for me. So, i can't even finish the activation... testing this method out, will report back...
EDIT: Ok, so using the "Tmobile Fix" didn't work for me, like i expected. BUT what did work for me, is, change the build.prop info like previously stated (Google Nexus, yakju, maguro) reboot, then update from marketplace. And it allowed me to add my debit card. Although it says "Unsupported device" up at the top, but it still let me open it and add my bank card. Will find out when i try to buy something...
Click to expand...
Click to collapse
So how did you get nfc on and working then?
Sent from my Galaxy Nexus using xda app-developers app
swa2k4 said:
So how did you get nfc on and working then?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
The .zip file is only for tw stock roms. You need to pull the apk and push it to system/app. Then do the build.prop edit to the galaxy nexus. Then reboot to cwm and wipe cache and Dalvik and fix permissions..reboot. profit!
Sent from my Galaxy nexus using Tapatalk 2
I went on the play store and was looking at all Google apps and I saw wallet it let me install it (fully stock non root) but when I open the app it says device not supported. But could it be that t-mobile is finally going to support Google Wallet, maybe its because their releasing the Nexus 4. Hopefully and has anyone else try this?
Thanks
Ram1500 said:
I went on the play store and was looking at all Google apps and I saw wallet it let me install it (fully stock non root) but when I open the app it says device not supported. But could it be that t-mobile is finally going to support Google Wallet, maybe its because their releasing the Nexus 4. Hopefully and has anyone else try this?
Thanks
Click to expand...
Click to collapse
work is ongoing...
http://forum.xda-developers.com/showthread.php?t=1956567
crazy talk said:
work is ongoing...
http://forum.xda-developers.com/showthread.php?t=1956567
Click to expand...
Click to collapse
yes but i believe that way you have to root and flash the app and change the build.prop, i was just saying that im fully stocked non root and locked bootloader. when you go on the play store it shows up and lets you install but the app wont work. maybe t-mobile will finally let us use it after they release the nexus?? just a thought lol
Ram1500 said:
yes but i believe that way you have to root and flash the app and change the build.prop, i was just saying that im fully stocked non root and locked bootloader. when you go on the play store it shows up and lets you install but the app wont work. maybe t-mobile will finally let us use it after they release the nexus?? just a thought lol
Click to expand...
Click to collapse
possibly, it will require a update specifically for the Note II on Google Wallets end (seems unlikely) or an update to our phone since we have some missing files inside the phone required to get Wallet up and running.
and in any case, T-mobile is knee deep in ISIS. i can't imagine them simultaneously supporting Google Wallet on all their phones. The Nexus 4 is an exception to the rule, not what we can expect going forward.
And about your phone, did your previous phones have Google Wallet?
crazy talk said:
possibly, it will require a update specifically for the Note II on Google Wallets end (seems unlikely) or an update to our phone since we have some missing files inside the phone required to get Wallet up and running.
and in any case, T-mobile is knee deep in ISIS. i can't imagine them simultaneously supporting Google Wallet on all their phones. The Nexus 4 is an exception to the rule, not what we can expect going forward.
And about your phone, did your previous phones have Google Wallet?
Click to expand...
Click to collapse
oh i guess i got my hopes up a bit, and yes they have but not stock i have the s3 but its running cm10 and the only one stock that had it was my old Galaxy Nexus, so i guess you can imagine how excited i got when i was able to install wallet on a fully stock phone, but oh well hopefully T-mobile will have a change of heart.
Hi developers!
Since the OOS 3.2.2 update, systemless root is now failing to pass googled safetynet checks, meaning Android pay no longer works :/ if I roll back to 3.2.1 then it works fine. I'm using the safetynet helped app from the play store to test this. I wondered if any developers or knowledgeable people would know if this is a change in the rom causing this, or just a SuperSU incompatibility?
OOS 3.2.2 validates with no root. I just flash SuperSU when needed and then unroot when finished. (TWRP as recovery) Some of my banking apps will not work with root installed.
Google made server side change that somehow now detects systemless root around 25th July.
spetrie said:
OOS 3.2.2 validates with no root. I just flash SuperSU when needed and then unroot when finished. (TWRP as recovery) Some of my banking apps will not work with root installed.
Google made server side change that somehow now detects systemless root around 25th July.
Click to expand...
Click to collapse
That might have been why then. Worked momentarily before the 3.2.2 update. Cheers for the info
manor7777 said:
Hi developers!
Since the OOS 3.2.2 update, systemless root is now failing to pass googled safetynet checks, meaning Android pay no longer works :/ if I roll back to 3.2.1 then it works fine. I'm using the safetynet helped app from the play store to test this. I wondered if any developers or knowledgeable people would know if this is a change in the rom causing this, or just a SuperSU incompatibility?
Click to expand...
Click to collapse
It's working for you on 3.2.1.? It stopped working for me on that version just prior to 3.2.2. coming out.
Google made changes sever side to prevent it from working. IT is getting to the point of having to pick. Root or android pay. We all knew this was coming.
Mit Hipster said:
It's working for you on 3.2.1.? It stopped working for me on that version just prior to 3.2.2. coming out.
Click to expand...
Click to collapse
It did momentarily but not for long. might have been a glitch or a slow-rollout on googles part. It's not working now!
zelendel said:
Google made changes sever side to prevent it from working. IT is getting to the point of having to pick. Root or android pay. We all knew this was coming.
Click to expand...
Click to collapse
Yeah we were waiting. Someone on XDA will find a way round at some point i bet, but we all knew it was coming!
manor7777 said:
Yeah we were waiting. Someone on XDA will find a way round at some point i bet, but we all knew it was coming!
Click to expand...
Click to collapse
If it was done server side there will be no work around. Plus with the new security measures in the linux kernel (XDA portal post) Things like this will be even harder if not impossible.
zelendel said:
If it was done server side there will be no work around. Plus with the new security measures in the linux kernel (XDA portal post) Things like this will be even harder if not impossible.
Click to expand...
Click to collapse
That's a fair point. Someone made a workaround before that worked for about 6 months through xposed, but to be honest I have twrp so I can flash what I need anyway, no biggie.
manor7777 said:
That's a fair point. Someone made a workaround before that worked for about 6 months through xposed, but to be honest I have twrp so I can flash what I need anyway, no biggie.
Click to expand...
Click to collapse
Yeah that will be the next thing they start looking for. Agreed doesnt really matter to me either. Mobile payments are banned everywhere I go and since I have to legally carry my ID around I also have my cards so even if it wasnt banned I still wouldnt use it.
zelendel said:
Yeah that will be the next thing they start looking for. Agreed doesnt really matter to me either. Mobile payments are banned everywhere I go and since I have to legally carry my ID around I also have my cards so even if it wasnt banned I still wouldnt use it.
Click to expand...
Click to collapse
That's a shame! Where are you based? Its EVERYWHERE in the UK!
manor7777 said:
That's a shame! Where are you based? Its EVERYWHERE in the UK!
Click to expand...
Click to collapse
I am in the US. It is available in most places just not in my town. After it was proven that it could be intercepted and the fact that stores are making their own alt to the pay apps, they decided to just block them.Even my Credit union has removed the chip from their cards due security concerns.
Like I said even if it was I still wouldnt use it. I am smarter then keeping things like my credit card info stored on a device that is always sending data everywhere. Mainly when you think about the fact that keyboards can record every keystroke.
Also I have to keep my ID on me at all times so it is just faster to take my card out and hand it to the cashier.
zelendel said:
I am in the US. It is available in most places just not in my town. After it was proven that it could be intercepted and the fact that stores are making their own alt to the pay apps, they decided to just block them.Even my Credit union has removed the chip from their cards due security concerns.
Like I said even if it was I still wouldnt use it. I am smarter then keeping things like my credit card info stored on a device that is always sending data everywhere. Mainly when you think about the fact that keyboards can record every keystroke.
Also I have to keep my ID on me at all times so it is just faster to take my card out and hand it to the cashier.
Click to expand...
Click to collapse
It's only stealable (like with card skimming) whilst the screen is on, at least on a phone. I have a card that I transfer money too whenever I use it (its actually my PayPal card) so I don't have too much of a risk there. They have done a few things like that over here in the UK too but I'm still cautious about it. I have a few measures in place to prevent some of that
manor7777 said:
It's only stealable (like with card skimming) whilst the screen is on, at least on a phone. I have a card that I transfer money too whenever I use it (its actually my PayPal card) so I don't have too much of a risk there. They have done a few things like that over here in the UK too but I'm still cautious about it. I have a few measures in place to prevent some of that
Click to expand...
Click to collapse
Thats all it really takes. When checked they found that the majority of the card readers had some sort of extra device installed on it. Like I said it is not a big deal for me as I wouldn't use it if it was available.
I was using systemless root for a while, it passed system checks just fine. But the funs over now, they've patched it. :/
Has anyone tried to see what works with some bloatware disabled & what doesn't work? Personally I would like the iris scanner and samsung pay to be enabled and everything else disabled.
Yeah, it's working for me quite well
XavierAD said:
Yeah, it's working for me quite well
Click to expand...
Click to collapse
Glad to hear it,arguably the best feature available for any Samsung device,short of root/ROMs.
Hopefully it'll still work once Android 7.0 rolls out.
KOLIOSIS said:
Glad to hear it,arguably the best feature available for any Samsung device,short of root/ROMs.
Hopefully it'll still work once Android 7.0 rolls out.
Click to expand...
Click to collapse
It will. They use Knox which is a product of Samsung.
Sent from my XT1528 using XDA Labs
I'm rather confused by this thread. Is the poster asking what will 'break' if you disabled all the bloatware? Or asking something else entirely? Cause you can disable everything that comes on any phone and it'll always work just fine.
And I have no idea what Android 7.0 would have to do with bloatware, or what KNOX would have to do with bloatware...
HikariNoKitsune said:
I'm rather confused by this thread. Is the poster asking what will 'break' if you disabled all the bloatware? Or asking something else entirely? Cause you can disable everything that comes on any phone and it'll always work just fine.
And I have no idea what Android 7.0 would have to do with bloatware, or what KNOX would have to do with bloatware...
Click to expand...
Click to collapse
I can't speak for the O.P.,but,my guess is, as with me, just making sure that it works before purchasing the Note 7,especially for those of us with the Snapdragon powered versions that may have no other way to disable bloat.
JMHO, but, the Q&A regarding functionality of PDP, whatever they may be, are of merit & might as well have a thread addressing the subject.
Most realize you can disable the bloat, but,not everyone, including yours truly, understand exactly how it works & why only on Samsung devices.
The Knox tie-in makes sense to me, even without a full understanding of how it works.
KOLIOSIS said:
I can't speak for the O.P.,but,my guess is, as with me, just making sure that it works before purchasing the Note 7,especially for those of us with the Snapdragon powered versions that may have no other way to disable bloat.
JMHO, but, the Q&A regarding functionality of PDP, whatever they may be, are of merit & might as well have a thread addressing the subject.
Most realize you can disable the bloat, but,not everyone, including yours truly, understand exactly how it works & why only on Samsung devices.
The Knox tie-in makes sense to me, even without a full understanding of how it works.
Click to expand...
Click to collapse
KNOX doesn't make much sense to me, because that's just a security platform. It just makes sure you protected from being 'hacked' per say. As in like, it adds an extra layer of security over your phone so someone can't just pick it up and plug it into a computer to gain access to all of your stuff. Though thats only the very loosest of analogies.
But I have to ask what you exactly mean by the "not everyone understands exactly how it works and why only on Samsung devices". Do you mean as in why disabling works? or something else. Because you can disable the bloatware on any android phone so long as the carrier and manufacturer didn't lock the option out. Which most devices will let you do it now because of the whole 'you'll get sued for forcing users to use a specific thing without giving them a way out' (an example would be microsoft getting sued over the bundling of Internet Explorer and Microsoft Office with the earlier Windows OS's).
What I'm wondering is, based on the title of the thread after thinking about it some, does the OP mean an app that disables/uninstalls bloat? Because I'm sure there are plenty of apps out there that do it. But most I think require Root in order to do it properly and reliably. I use Sprint for my service, and its Sprint ID and such are a pain in the ass, and they can't just be 'disabled' easily even though there is the option to (every time you disable it, Sprint just re-installs it the next time you reboot the phone because it thinks it got uninstalled somehow). But to get it to disable properly on my Note 5, I had to install some random app that I think was called App Quarantine. It looked like a bio-hazard symbol for the icon. I haven't re-installed it since this last wipe I was forced to do, so I can't remember exactly lol. But it was the only one that would let me actually disable the Sprint ID stuff and not have it re-install all the time.
HikariNoKitsune said:
What I'm wondering is, based on the title of the thread after thinking about it some, does the OP mean an app that disables/uninstalls bloat? Because I'm sure there are plenty of apps out there that do it.
Click to expand...
Click to collapse
Yes it's an app in the Google Play Store that has the ability to disable literally anything on Samsung devices,WITHOUT ROOT, so, care must be taken to not get carried away & I recommend only disabling, not deleting, in the event of not being able to take an update otherwise.
Not everything can be disabled natively, so, that explains the appeal of the app.
If you used it, you'd see the tie-in with Knox........
KOLIOSIS said:
Yes it's an app in the Google Play Store that has the ability to disable literally anything on Samsung devices,WITHOUT ROOT, so, care must be taken to not get carried away & I recommend only disabling, not deleting, in the event of not being able to take an update otherwise.
Not everything can be disabled natively, so, that explains the appeal of the app.
If you used it, you'd see the tie-in with Knox........
Click to expand...
Click to collapse
Then that makes alot more sense. I originally just thought they were basically asking if there was an app to disable everything instead of having to do it manually. I've always just manually disabled everything cause its not that hard to do. Just find the troublesome things and hit that disable button lol. But if this can do it all in one quick swoop, then I'm all in =O I'll definitely be looking into it later today when my phone finally arrives...
Sprint screwed up my pre-order, and is sending me the wrong device, so I have to take it into a store to get it exchanged because they refused to cancel my pre-order or change the order at all even though I legitimately ordered the dang thing 2 minutes past midnight on the 3rd. So ontop of that, they also didn't ship the phone when they said they would, AND the put restrictions on my package. I normally have to physically go to a UPS location to pick up my packages cause the dumb driver will never deliver to my house... always states that they can't find my house even though its the ONLY house down the ONLY long driveway... heck you can SEE my house above the trees! But nope, the guy wont deliver. But because of the restrictions, UPS wont let me flag the package as 'hold for pickup' like usual, so I gotta stand at the end of my drive way for hours upon hours just to catch the UPS driver. Then I gotta drive all the way into town to HOPEFULLY exchange the phone for the Black Onyx variant that I was supposed to get...
Anyway, sorry for the ramble o-o; didn't realize it was that long XD
HikariNoKitsune said:
Then that makes alot more sense. I originally just thought they were basically asking if there was an app to disable everything instead of having to do it manually. I've always just manually disabled everything cause its not that hard to do. Just find the troublesome things and hit that disable button lol. But if this can do it all in one quick swoop, then I'm all in =O I'll definitely be looking into it later today when my phone finally arrives...
Click to expand...
Click to collapse
It's a nice tool to have, a powerful one.
Just a friendly piece of advice :
Read up on it before using, check the FAQs on the developers site if need be & go conservative at 1st if you're not familiar with what is safe to disable.
The app gives color-coded guidelines per each app on what is known to be safe to disable. You can go above and beyond that, but, mainly, just disable, do not delete anything & leave the stock keyboard alone.
You might be able to disable the stock launcher, provided you have another one installed, but, I'd leave it alone until you're certain one way or the other........
KOLIOSIS said:
It's a nice tool to have, a powerful one.
Just a friendly piece of advice :
Read up on it before using, check the FAQs on the developers site if need be & go conservative at 1st if you're not familiar with what is safe to disable.
The app gives color-coded guidelines per each app on what is known to be safe to disable. You can go above and beyond that, but, mainly, just disable, do not delete anything & leave the stock keyboard alone.
You might be able to disable the stock launcher, provided you have another one installed, but, I'd leave it alone until you're certain one way or the other........
Click to expand...
Click to collapse
Lol I'd only disable the things I already know I need to disable. Like all the Sprint stuff. I leave the Samsung stuff alone cause I actually use alot of Samsung's things. But as for Sprint's stuff? All of that goes bye bye lol. Now that is assuming it doesn't somehow show things that you normally can't see from the applications manager. In which case then I wouldn't bother, cause I don't see much of a point lol.
there are a few package disabler for Samsung out there, which one the best?
amenlo9 said:
there are a few package disabler for Samsung out there, which one the best?
Click to expand...
Click to collapse
Go with either one,the Pro+ has a hardware lockdown feature,otherwise,there two are identical:
https://play.google.com/store/apps/details?id=com.ospolice.packagedisablerpremium&hl=en
https://play.google.com/store/apps/details?id=com.ospolice.packagedisablerpro&hl=en
I'm guessing Samsung still has a partnership w/Cheetah Mobile,which is one of the main reasons I like having this app,Package Disabler Pro,on-board to ward off the data mining/crapware/etc...
However,I'm not seeing anything in the apps,system or otherwise,that's jumping out & identifying itself as CheetahMobile/CleanMaster/etc.......
I'm guessing it's some/all of the apps identified w/the "Smart" moniker,but,I'm not 100% certain on that.
Anyone have an idea on which,if any,of the apps are actual CheetahMobile bloatware?
Thanks In Advance!
Using EZ Disabler here. Works well, but you gotta be careful using "disable bloat" part as it will turn off many useful things. I just went through and picked what i wanted. Very Easy to use though
Thanks for recommending Package Disabler Pro. I was worried Since not rooted. In past had always used TB . This worked Great!!
Sent from my SM-N930P using Tapatalk
Why would you guys use an app for disabling stuff.
Since we're on xda, enable USB debugging and use pm (package manager) cmd from adb shell.
For instance: adb shell pm hide 'package'
There are other interesting options: list, install, uninstall.
Sent from my HTC One using Tapatalk
millicent said:
Why would you guys use an app for disabling stuff.
Since we're on xda, enable USB debugging and use pm (package manager) cmd from adb shell.
For instance: adb shell pm hide 'package'
There are other interesting options: list, install, uninstall.
Click to expand...
Click to collapse
I see your point, but i would also say there is a ease to the app though. Whatever works best for people. Im just glad there are options.