Would someone be able to decompile this visual voicemail apk from my cell provider Fido and see if they can set permissions so its not restricted to run on the Samsung galaxy s 2? Its currently restricted to run on the Samsung Galaxy Q
JPHCCFC said:
Would someone be able to decompile this visual voicemail apk from my cell provider Fido and see if they can set permissions so its not restricted to run on the Samsung galaxy s 2? Its currently restricted to run on the Samsung Galaxy Q
Click to expand...
Click to collapse
Its available from the market for SG2:https://market.android.com/details?...vbS5waG9uZWZ1c2lvbi52b2ljZW1haWxwbHVzLmFuZCJd
russpattaya said:
Its available from the market for SG2:https://market.android.com/details?...vbS5waG9uZWZ1c2lvbi52b2ljZW1haWxwbHVzLmFuZCJd
Click to expand...
Click to collapse
That's a different app and not compatible over here in Canada. The one I attached is provided by the Canadian network fido and at present it is restricted not to work on the Samsung galaxy s2 for some bizarre reason. I was hoping it would be an easy change in a line of code to enable its use on the s2 hence the request to decompile.
I'm with Fido on my HTC One X and would love to see this happen to. I'd post a bounty if anyone is interested in doing the work.
Understanding google wallet
the new google wallet is now available on ALL devices, however the "tap and pay" feature isn't
the tap and pay feature is officially only supported on the following devices
Phones
HTC One on Sprint
HTC One SV on Boost Mobile
HTC EVO 4G LTE on Sprint
LG Viper 4G LTE on Sprint
LG Viper 4G LTE on Zact Mobile
LG Optimus Elite on Sprint
LG Optimus Elite on Virgin Mobile
LG Optimus Elite on Zact Mobile
LG Nexus 4*
Motorola Moto X on Sprint
Motorola Moto X on US Cellular
Samsung Galaxy Note II on Sprint
Samsung Galaxy Note II on US Cellular
Samsung Galaxy SIII on Sprint
Samsung Galaxy SIII on MetroPCS
Samsung Galaxy SIII on US Cellular
Samsung Galaxy SIII on Virgin Mobile
Samsung Galaxy SIII on Boost Mobile
Samsung Galaxy S4 on Sprint
Samsung Galaxy S4 on US Cellular
Samsung Galaxy S4 Google Play Edition*
Samsung Nexus S 4G on Sprint
Samsung Galaxy Nexus on Sprint
Samsung Galaxy Nexus*
Samsung Galaxy Victory 4G LTE on Sprint
Samsung Galaxy Victory 4G LTE on Virgin Mobile
Samsung Galaxy Axiom on US Cellular
Tablets
ASUS Nexus 7 (2012)
ASUS Nexus 7 3G (2012)*
Samsung Nexus 10
other phone can support tap and pay.... they just need a work around
for google wallet (TAP) to work first your nfc libs need to be correct (smx enabled)
and second the google servers need to see that your phone is supported for the initial setup (build.prop edit)
for example, if you have an AT&T galaxy s3, the smx (most likely) is not enabled because they want you to use ISIS (which uses the secure element in the sim card)
We cannot compile the att version of touchwiz because we have no source, we can take the correct libs from a sprint gs3 to use on an att phone (see lib fix below)
When trying to get wallet to work on a new device/rom take the following steps
1-instal wallet from play or side load. Set up and see if tap and pay is enabled. if no, see step 2
2-change build.prop to galaxy nexus (see below) uninstall wallet then reboot and repeat step 1. if no, see step 3
3-run a logcat while opening wallet and look for "wallet" , "nfc" , and "smx" . Most likely at this point you need a (lib fix) In other words, you need the smx enabled libraries and corresponding files from a supported device. flash appropriate files (see lib fix zip) and start at 1
4-once google wallet TAP is working, the build.prop can be reverted, but sometimes is will break wallet (TAP) and it might take a couple times for success. keeping the build.prop as galaxy nexus has no real side effects (I currently have a sony galaxy nexus )
old wallet fix
*The lib&nfc fix is intended touchwiz roms
For CM9/10,aokp, and any other aosp rom, just flash the desired version wallet as the libs and nfc apk are correct
latest Wallet version 1.5-r87-v15 changelog
where google wallet works
Google wallet (rom) compatibly list
to contribute here is the google wallet compatibly list thread
Ok, first a little background
basically what you are seeing if you try to install google wallet on at&t, tmo, etc, is you get stuck on "activating device"
If you dig a little further and ran a logcat, you will see that there it no "SMX detected"
What this means, when compiling the rom you need to enable SmartMX in the config headers located in the external/libnfc-nxp library. (thats why it works on CM9/10, they do this)
this is impossible for us because there is no source for samsung's TouchWiz. We got a break on the international sgs3 as the latest update has the secure element enabled...so does the sprint sgs3
well that got me thinking, and of course sprint's nfc libs are close enough to work without breaking anything
so this is how to do it. (btw, you need root)
1-make a nandroid! I am not responsible if you mess up your device
2-edit you build.prop using root explorer (when you press save, it creates a build.prop.bak)
do not use ES explorer, it does not save correctly, for that matter ONLY use root explorer! (or adb push/pull)
/system/build.prop
preferred
Code:
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
or
Code:
ro.product.model=htc_jewel
ro.product.name=htc_jewel
ro.product.device=htc_jewel
3-If you already have Wallet installed...open wallet, go to settings and "reset google wallet" (if it hangs at 99%, reboot and continue with steps)
(if you are (re)installing a new rom, this applies too...reset google wallet from within app)
4-boot to recovery and flash SGS3-TW-US_variants-lib&nfc-fix.zip for ics touchwiz roms or SGS3-TW-US_variants-lib_nfc-fix-jellybean_4.1-1.zip for jellybean touchwiz roms and then wallet version com.google.android.apps.walletnfcrel.modaco.1.5-r87-v15.zip
(for CM9/10, I9300, aokp, aosp roms just flash the wallet zip)
5-reboot device, you will get "android is updating" (only this first boot)(all apps)
6-open google wallet and sign in. add your personal credit cards (you must add them from your desktop first if you have never used google checkout before)
7-(optional)if you get "error adding card try again later", wipe cache and davlik cache from recovery (only once! it sometimes takes hours, not minutes)
8-profit (hold on! your not done, continue on to steps 9 & 10)
9-after it is all up and running (meaning cards added), mount r/w in root explorer, delete the modded build.prop, then rename build.prop.bak to build.prop
10-make a new nandroid with working wallet and put it in a safe place in case you ever accidentally install a new ROM without resetting google wallet data.
still confused, here is a video of how to do it by moonfire711
step by step upgrading to jellybean and adding wallet for verizon here
>Special thanks to Hammermann, he did a ton of nandroids! He confirmed for me that the sprint nfc libs worked
>Special thanks to WarlockLord we now have success on verizon
>thanks to mobilehavoc for the galaxy nexus build.prop tip
>thanks to magn2o for patching the new wallet (until paul returned)
>thanks to FreydNot for for the above tip and for being brave enough to be the first to flash this to his tmobile sgs3
>thanks to chris.ayoubtexas, the first att user with success (beat out Hammerman because ES explorer was screwing him)
>thanks to Maldewka for installing and confirming functionality on US Cellular
>thanks to Paul at Modoco for the modded google wallet apk<<<Paul's thread
Click to expand...
Click to collapse
notes*
-if you have used google wallet on another device, your prepaid card on the sgs3 is not the same...so balances will not carry over on the prepaid card prepaid is finished
-despite the new cloud-based authentication system, the app does not require the phone to have a data connection to make payments at NFC-equipped terminals
-really the key to this fix is the libs with the security element enabled.
-the build.prop edit is for enabling cards, once they are enabled it can be reverted
-the wallet apk has 3 features patched out. The first was a device check, the second patch was an operator check and the third patch was removing the root warning
-NEVER, I REPEAT NEVER RESTORE GOOGLE WALLET WITH TITANIUM BACKUP! (please click link on step 10)
original build.prop values for at&t
Code:
ro.product.model=SAMSUNG-SGH-I747
ro.product.name=d2uc
ro.product.device=d2att
original build.prop values for t-mobile
Code:
ro.product.model=SGH-T999
ro.product.name=d2tmo
ro.product.device=d2tmo
original build.prop values for US Cellular
Code:
ro.product.model=SCH-R530U
ro.product.name=d2usc
ro.product.device=d2usc
original build.prop values for verizon
Code:
ro.product.model=SCH-I535
ro.product.name=d2vzw
ro.product.device=d2vzw
original build.prop values for Telus, Rogers, Bell
Code:
ro.product.model=SGH-I747M
ro.product.name=d2vl
ro.product.device=d2can
original build.prop values for Wind Mobile
Code:
ro.product.model=SGH-T999V
ro.product.name=d2vw
ro.product.device=d2can
stop! if you are unclear of what to download, read the instructions again
newest files are at the bottom[/HIDE]
Guess I'll finally have to root.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Cool info, thanks for sharing I won't be using it cause I flash too many roms and I'll forget to this every time, but I appreciate your contribution
Sent from my SGH-T999 using Tapatalk 2
It doesn't work. I am stuck at verifying money network.
Sent from my HTC amaze using xda premium
Followed the instructions. Phone went into a boot loop. Had to restore from my Android.
I'll try again later tonight, maybe I messed something up.
Odexed said:
It doesn't work. I am stuck at verifying money network.
Sent from my HTC amaze using xda premium
Click to expand...
Click to collapse
that can take some time, its not always within 5 mins (it can take hours)
if you get an error adding card, post a logcat while doing it
EvilEvo said:
Followed the instructions. Phone went into a boot loop. Had to restore from my Android.
I'll try again later tonight, maybe I messed something up.
Click to expand...
Click to collapse
are you running a modified rom? it doesn't seem to work (bootloops) with DIET ICS rom
Do not use ES explorer to edit
SUCCESS!!! I got google wallet working on my T-Mobile USA GS3 (t-999) running the Free GS3 R3 ROM by following the OP instructions. It hung for several minutes trying to add the google prepaid card but it finally came around. I was on my home wifi if that makes a difference for anyone.
I'm going out on a limb here to guess you could use the build.prop strings from the Sprint GS3 instead of htc_jewel since that is the origin of the NFC library files but I guess as long as it works it doesn't really matter. I used htc_jewel as instructed in the OP.
I would add the following to your instructions:
1.5 - make a backup copy of your build.prop file
8 - once you have verified everything is working, put your backup copy of build.prop back in place and reboot
Edit: Also, it would be a good idea to make a nandroid backup once wallet is working and store it somewhere safe. That way you can restore to a working config if you accidentally install a new ROM without resetting google wallet data.
I tried it on AOKP (7.12.2012 Build) and I can get past the "this device is not supported" stage and through to the Terms and Condition page but when I click agree, it tells me NFC needs to be enabled and "exit" "settings" menu option pops up. I click on settings which takes me to "more..." under settings which displays "airplane", "VPN", "tethering", etc but no NFC options.
If I remember correctly, on yesterdays release, NFC was there in all it's glory with the option for lockscreen, etc... But now, it's no where to be found.
I guess I'll be posting this to the AOKP forum (task650 and ktoonsez) and see what they say.
FreydNot said:
SUCCESS!!! I got google wallet working on my T-Mobile USA GS3 (t-999) running the Free GS3 R3 ROM by following the OP instructions. It hung for several minutes trying to add the google prepaid card but it finally came around. I was on my home wifi if that makes a difference for anyone.
I'm going out on a limb here to guess you could use the build.prop strings from the Sprint GS3 instead of htc_jewel since that is the origin of the NFC library files but I guess as long as it works it doesn't really matter. I used htc_jewel as instructed in the OP.
I would add the following to your instructions:
1.5 - make a backup copy of your build.prop file
8 - once you have verified everything is working, put your backup copy of build.prop back in place and reboot
Edit: Also, it would be a good idea to make a nandroid backup once wallet is working and store it somewhere safe. That way you can restore to a working config if you accidentally install a new ROM without resetting google wallet data.
Click to expand...
Click to collapse
sweet. you might be the first with a tmobile sgs3 with a working google wallet (using tw)
I will add to the op...yes, as far as the build.prop, it really doesn't matter...that is just what worked for me. I will add though, after you get it up and going, you can put your stock build.prop back in...
meccanikal said:
I tried it on AOKP (7.12.2012 Build) and I can get past the "this device is not supported" stage and through to the Terms and Condition page but when I click agree, it tells me NFC needs to be enabled and "exit" "settings" menu option pops up. I click on settings which takes me to "more..." under settings which displays "airplane", "VPN", "tethering", etc but no NFC options.
If I remember correctly, on yesterdays release, NFC was there in all it's glory with the option for lockscreen, etc... But now, it's no where to be found.
I guess I'll be posting this to the AOKP forum (task650 and ktoonsez) and see what they say.
Click to expand...
Click to collapse
aokp need cm9 libs they are aosp builds not samsumg...
should be easy to get it working though...wallet works fine on cm9
So instead of using htc_jewell you used Sprint_GS3?
sent from my GALAXY SIII
manny05 said:
So instead of using htc_jewell you used Sprint_GS3?
sent from my GALAXY SIII
Click to expand...
Click to collapse
FreydNot said:
I'm going out on a limb here to guess you could use the build.prop strings from the Sprint GS3 instead of htc_jewel since that is the origin of the NFC library files but I guess as long as it works it doesn't really matter. I used htc_jewel as instructed in the OP.
Click to expand...
Click to collapse
If you are asking me, I used htc_jewel (only 1 L), but I speculated on being able to use others.
manny05 said:
So instead of using htc_jewell you used Sprint_GS3?
sent from my GALAXY SIII
Click to expand...
Click to collapse
FreydNot said:
If you are asking me, I used htc_jewel (only 1 L), but I speculated on being able to use others.
Click to expand...
Click to collapse
the sprint one might work...but it doesn't matter. your going to put your stock one back in anyways
FreydNot said:
If you are asking me, I used htc_jewel (only 1 L), but I speculated on being able to use others.
Click to expand...
Click to collapse
you did the one line edit? which one? model? I can adjust the op...
FreydNot said:
If you are asking me, I used htc_jewel (only 1 L), but I speculated on being able to use others.
Click to expand...
Click to collapse
Ah. Idk how I missed that last sentence lol. I'm gonna give this a try
sent from my GALAXY SIII
Working on ATT, stock!
what is the sprint gs3 model, device, and name?
htc_jewel makes NFC disappear in AOKP
meccanikal said:
what is the sprint gs3 model, device, and name?
htc_jewel makes NFC disappear in AOKP
Click to expand...
Click to collapse
not the build prop. you need cm9 libs for aokp
ogdobber said:
are you running a modified rom? it doesn't seem to work (bootloops) with DIET ICS rom
Click to expand...
Click to collapse
Nope. Stock rom, just debloated some myself and some other apps frozen.
Being one of the lucky ones to own a Galaxy S4, I have had the privilege of running the Android 4.3 Leak.
It seems that there is an additional protection on the nfc secure element. If a ROM has been deodexed it will fail a tamper protection check, and refuse to grant access. Applications like google wallet use this to securely store, access, and transmit data using the NCF chip. Now, since this is a google branded release it is somewhat concerning that the protection is showing up. This could still be the influences of Samsung on the device, but that still remains to be seen. I eagerly await the release of additional Android 4.3 updates, and as always only time will tell if this is a new feature of 4.3 or if it is vendor specific.
In the mean time here is a writeup on how to bypass this new protection:
http://forum.xda-developers.com/showthread.php?t=2361183
I got the brand new T Mobile Samsung Galaxy S6 Edge and love using it. I figured out that S Beam option is not available in the device to beam photos or videos. I found out that S Beam app is
listed out in the Apps section under Application Manager --> Applications --> All.
So I think S Beam app is shipped along with the device but for some reason it was not installed or enabled. I would like to know why it was not installed on the device. Is there any way to install S Beam app. BTW, my device is not rooted.
praveengoparaju said:
I got the brand new T Mobile Samsung Galaxy S6 Edge and love using it. I figured out that S Beam option is not available in the device to beam photos or videos. I found out that S Beam app is
listed out in the Apps section under Application Manager --> Applications --> All.
So I think S Beam app is shipped along with the device but for some reason it was not installed or enabled. I would like to know why it was not installed on the device. Is there any way to install S Beam app. BTW, my device is not rooted.
Click to expand...
Click to collapse
Hi there, unfortunatly the cool S-beam Feature found on previous galaxy devices was not developed for the Galaxy S6 nor the S6 edge.
the S-beam feature was sacrificed in order to to launch the new Samsung feature of wireless charging . it is still a great phone though with many other awesome features and hope you will enjoy it.
Nick795 said:
Hi there, unfortunatly the cool S-beam Feature found on previous galaxy devices was not developed for the Galaxy S6 nor the S6 edge.
the S-beam feature was sacrificed in order to to launch the new Samsung feature of wireless charging . it is still a great phone though with many other awesome features and hope you will enjoy it.
Click to expand...
Click to collapse
I had no idea where you get the information that S-Beam is sacrificed for the wireless charging. I personally thinks that wireless charging has nothing to do with S-Beam whatsoever (S4 and S5 can still have S-Beam even after using the special case for wireless charging).
S-Beam is working in S6, just differently (you can find "S Beam" in the Application Manager). Try beaming photos/videos from another Samsung device, and you'll notice the File Transfer is very fast. However the problem lies with sending from S6. For some reason Samsung limits this feature to just receiving files. If anyone finds out how to access the S-Beam feature and enabling it for sending as well please share.
Edit: Wireless Charging is not a "new" feature. Samsung just decided to include it in the phone since it doesn't have removeable battery anymore = no more removable back cover.
Anyone get Samsung Pay to work on a rooted non Samsung phone? I used Magisk hide to hide root for Samsung Pay, but that does not work. Is this something that is just not possible?
thanks
Samsung Pay requires a Samsung phone, and a non-rooted one at that.
(edit - at least that's what I think. I know on a Samsung phone, once you root and trip Knox, you are unable to use Samsung Pay permanently on that device)
thanks, i have read it will work with the watch and a non Samsung phone. I was surprised that magisk hide was not enough to make it work...
I am having OnePlus 5T non rooted with Galaxy watch WiFi edition and it does not still work. I am from India.
I think it used to work with OnePlus 5T and Gear S3 with the gear S3 watch plugin and Samsung pay plugin. The same plugin does not work with Galaxy watch.
We need to wait for Samsung to provide the suppory for Samsung pay along with the watch plugin.
Sent from my ONEPLUS A5010 using Tapatalk
I uninstalled samsung pay, reinstalled and before opening used magisk hide and now it let me set it up. have not had a chance to use it yet.
Use magisk hide to hide root from ALL Samsung apps you will find on your phone. Got a non-samsung phone, had struggles at the beginning too, until I did this, and now it works.
I just updated Samsung Pay on my OP5 and it wouldn't open,l because the phone is rooted. It was working just before the update.
I was able to get it working again by turning off storage permissions for the Samsung Pay watch plug-in and then allowing it again when the app asked for it. Unexpected, but I'll take it.
Rooted 6T here. SPay works fine with Magisk v19 beta.
Sent from my ONEPLUS A6013 using Tapatalk