Senior Member - OP
Thanks Meter 96
Posts: 354
Join Date: May 2007
Location: Salt Lake City, UT
|
[WIP] Isis Wallet
Although ISIS Wallet has been discussed in the Google wallet forum, I thought it might be more productive to have a dedicated ISIS thread instead:
I spent an hour or so today attempting to get Isis Wallet working on my DNA. I got a SIM card with Secure Element about a week ago, but hadn't had time to work on it. I should also indicated that I live in SLC, UT, one of the initial areas where ISIS is being rolled out. However, it seems that ISIS might be going through a "soft release" - apparently anyone can order a sim w/ secure element now. There are reports of ISIS working outside of SLC and Austin.
My first attempt was to install ISIS on a Viper ROM (I am also s-off). The initial running of the app failed from the beginning with an error about root. I then attempted using Voodoo Root to hide root. Still failed.
I then installed a basic 2.04 rom, which was rooted, although I deleted su and superuser from the install before before booting into the ROM. I installed the ISIS apk I have (since it won't show up on the app store). This time, I was greeted with a screen prompting me to set up an ISIS account. I entered my email address (it actually pulled this from my first gmail account) and created a password. Next, I was prompted to accept the TOS and then create a PIN. I then got message to wait while the secure element was activated. It indicated that I would receive a sms when activated. Instead, I received an email that it had failed, and to contact my provider.
I then modified the build.prop to look like a DInc 4g LTE (which is an authorized device for ISIS). This time, ISIS was actually available in the Play Store (although I had it already installed). As I ran the app, I got to the point of creating a PIN, and then I got a message "Wallet Activation Error - ISIS is not supported for your device".
That is as far I got. I find it interesting that with a modified build.prop, I get an error that I have a wrong device. I don't know where else Isis is checking for my device, but I'm out of ideas. Anybody else?
|