HTC one x at&t and google wallet
- Thread starter Oridus
- Start date
Agreed. Greedy.
Ive been holding off on updating to 2.20 so i can keep my root and hopefully figure out a way to get this to work. (just stuck on the "release-keys" error)
Im about to give up and just update my HOX.
Ive been keeping an eye on this isis crap (that what it is) and they really haven't said much about it. Im just tired of waiting to catch up to the rest of the world.
Ive been holding off on updating to 2.20 so i can keep my root and hopefully figure out a way to get this to work. (just stuck on the "release-keys" error)
Im about to give up and just update my HOX.
Ive been keeping an eye on this isis crap (that what it is) and they really haven't said much about it. Im just tired of waiting to catch up to the rest of the world.
Thats what I was thinking too...because that's what I had to do to get it to work on my ATT Galaxy S3, but we flashed a modified GWallet also I believe...
What changes do we need to make? I looked in the Evo LTE wallet thread and didn't see any info.
Tried build.prop edit to
ro.product.model=htc_jewel
ro.product.name=htc_jewel
ro.product.device=htc_jewel
Jewel is the Evo 4G LTE internal name.
Market version of Wallet doesn't start, unsupported device or carrier. Patched version from Modaco starts but gives the release-keys error everyone's been getting.
Maybe try changing the carrier name in build.prop to Sprint or something. Otherwise, the reason is probably that the NFC libs in our One X roms weren't compiled to support Wallet (try copying them over from the Evo?)
edit: got past release-keys error but
D/NFC JNI ( 786): phLibNfc_SE_GetSecureElementList()
D/NFC-HCI ( 786): HTC: phLibNfc_SE_GetSecureElementList
D/NFC JNI ( 786):
D/NFC JNI ( 786): > Number of Secure Element(s) : 0
in order to get past "phLibNfc_SE_GetSecureElementList(): No SMX detected" we need secure element support in our nfc libs, either recompile nfc libs with SmartMX support or try copying from EVO 4G LTE (which didn't work according to this thread)
ro.product.model=htc_jewel
ro.product.name=htc_jewel
ro.product.device=htc_jewel
Jewel is the Evo 4G LTE internal name.
Market version of Wallet doesn't start, unsupported device or carrier. Patched version from Modaco starts but gives the release-keys error everyone's been getting.
Maybe try changing the carrier name in build.prop to Sprint or something. Otherwise, the reason is probably that the NFC libs in our One X roms weren't compiled to support Wallet (try copying them over from the Evo?)
edit: got past release-keys error but
D/NFC JNI ( 786): phLibNfc_SE_GetSecureElementList()
D/NFC-HCI ( 786): HTC: phLibNfc_SE_GetSecureElementList
D/NFC JNI ( 786):
D/NFC JNI ( 786): > Number of Secure Element(s) : 0
in order to get past "phLibNfc_SE_GetSecureElementList(): No SMX detected" we need secure element support in our nfc libs, either recompile nfc libs with SmartMX support or try copying from EVO 4G LTE (which didn't work according to this thread)
Last edited:
I highly doubt Google bargaining power is lower than Apple's. Google controls Android and without Android the networks will have to eat Apple's **** all the time.
If you could not tightly integrate your phone with gapps would you touch it? I certainly would not. For some reason they have chosen to be accommodating, we can only guess why. With the current arrangements you can use Google voice over an edge network in the middle of nowhere to call anywhere in the world. Try doing that with Skype.
I would not be so sure. Most users have a lot more excess cell minutes than data. For the little while that I tried an iThingie I had to disable I message iMessage because it was eating up bandwidth for picture messages. Plus, cell coverage is A LOT more robust and widespread than 3g coverage that would be required for VoIP
Last edited:
@KitF
I've been trying this, but to no avail. It gets you a step past the keys error, but hangs at "Activating your device..." I've also tried using the evos build prop, which didn't change anything.
I've been trying this, but to no avail. It gets you a step past the keys error, but hangs at "Activating your device..." I've also tried using the evos build prop, which didn't change anything.
Last edited:
I had this working on some diff. Devices a while back, now that I have a hox again, this I can't get it working in......replacing the lib files from the evo lte causes it to freeze on boot so that won't work......as said above we need to rebuild our own .so files for secure element........
Sent from my HTC One X+ p_type 0.91.0
HTC One XL
I don't understand why this app isn't available on the HTC One XL (Australia) as it is NFC capable and has the option to enable along with beam in settings...
Yet when I try to download it from the Play store, I get a message saying that it is incompatible with my device??
Do you know if there is any way this app can work on the One XL or if it will in the future?
I don't understand why this app isn't available on the HTC One XL (Australia) as it is NFC capable and has the option to enable along with beam in settings...
Yet when I try to download it from the Play store, I get a message saying that it is incompatible with my device??
Do you know if there is any way this app can work on the One XL or if it will in the future?
Hopefully someone is still monitoring this thread.
I recently got an AT&T One X, I'm using it with Straight Talk though, the phone is also SIM unlocked. I installed a rooted version of the new JB Sense ROM for the phone, and have tried getting GW to work using the patched APK's and by editing the build.prop file, and still get the secure element error. I tried running a CM 10.1 nightly on the phone already, but it was the most unstable CM I've ever used, so went back to Sense for now.
My question is though, will GW work without any problem if I'm running CM 10.x? Is it only crippled on official software? If it will work on CM, I may tried CM 10 instead of 10.1.
no apk, ROM, or prop editing will get it going currently. It's going to take some work. H8rift (our cm maintainer) said he'll try it eventually but with cm10.1 and h8 working on a major kernel upgrade it could be awhile.
There's hope, just no timetable.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
3All this and it doesn't work and you still didn't try it so you wouldn't know. This thread is hysterical.
Alright I tried it. It doesn't work. But that isn't the point. When the bickering started it was all triggered by your "Brilliant Rolleyes" comment preceded by your "You didn't even try it but post like you know it works." Well two things 1) I didn't post like I know it works ...I only referred people to have a look and I said that it "seems" like it works. That is a disclaimer!!! So no I didn't post like I know it works. 2) Secondly your "Brilliant Rolleyes" is rude
So I was wrong in my later comments but that was not my initial stand on the matter. but you were rude which is worse. So so is everyone else that contributed instead of being a little more pleasant.
Maybe we can all get along now and everyone should reflect and realize that if you attack someone that the initial reaction is to attack back....even if they are misguided. That is not a good way to behave....on both sides.2Paul O'Brien got it working for all versions of the HOX:
https://twitter.com/PaulOBrien/status/207467919590957056
He said he should be able to upload the .apk tomorrow! Can't wait
