Semble SIM: compatible handsets

Forums › One New Zealand (including Vodafone, WxC, Farmside) › Semble SIM: compatible handsets

1 | ... | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | ... | 17

1710 posts

Uber Geek

Trusted

#1278601 7-Apr-2015 19:16

I have a One max as well, AFAIK it supports the same APIs as the M7 as they're near-identical. Believe 2d has not given Semble samples for testing, although I could well be wrong as we do not have visibility over other network operators' test lists.

Product Manager @ PB Tech

Smartphones @ PB Tech | Headphones @ PB Tech

richms

28172 posts

Uber Geek

Trusted

Lifetime subscriber

#1278604 7-Apr-2015 19:20

I messaged ASB about the second pair of fake cards not shiwing up to put a pin on and the text to add a pin came thru later and I was able to put a pin on them and buy some stuff with my note4 so it just looks like their system isnt really set up to handle an additional phone connecting to the same cards, but it has ended up working fine.

Richard rich.ms

Xeon

302 posts

Ultimate Geek

#1278645 7-Apr-2015 20:06

Hm,
Bought a Vodafone Smart 4 Turbo for testing. Loaded ASB card and tested a few times with the self checkouts at New World, too many cards/cant read error when the phone was sleep or turned off but worked straight away with phone on.
Also took the sim out and put in my OnePlus One, was greeted by Declined, Card Blocked by the reader but it did obviously pick up there was something there.

freitasm

BDFL - Memuneh
79263 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1278647 7-Apr-2015 20:12

The not working with the handset off and the "declined" message is likely because you have not selected a default card within the Semble app and did not check the option for always use that card. I had the same when I first tried on my M9 and it worked after checking this.

Also on Settings | NFC | Tap & Pay make sure the Semble is the selected one on your OnePlus One.

Xeon

302 posts

Ultimate Geek

#1278679 7-Apr-2015 21:31

I do have a card set to always on mode but Oneplus one doesn't have the openmobileapi so you can't install semble.

I'm guessing the oneplus is just sending some default card to the reader since it will only connect when the phone is on. Whereas if it was using SWP it should work all the time.

Scanning the turbo smart 4 with my one plus tells me its Visa smartcard, scanning my oneplus with the turbo smart 4 doesn't tell me anything.

Anyway going to build CM12 with the Openmobileapi and see what happens (if I have the time).

samo

22 posts

Geek

#1278710 7-Apr-2015 22:23

Can someone tell me how the app is checking the phone model? I just wanna try it out

roobarb

653 posts

Ultimate Geek

Trusted

#1278716 7-Apr-2015 22:58

When a contactless card is presented to a terminal, the first thing a terminal does is ask for the PPSE. This is basically a default entry point for the terminal to determine what payment instruments are available and what their priority is.

When the credit card is set to 'always on' by the Semble app, the SIM will provide the PPSE listing that credit card, this information is persistent on the SIM, else it would not survive power off or being put in another handset.

When you are in the mode where the Semble app is running, I don't know what component constructs the PPSE, it could be the SIM, it could be an HCE style component, it could be the Semble app telling the SIM to respond just once with this credit card based on detection of entry into the RF field.

Wise

Send money globally for less with Wise - one free transfer up to NZ$900 (affiliate link).

Xeon

302 posts

Ultimate Geek

#1278719 7-Apr-2015 23:12

samo: Can someone tell me how the app is checking the phone model? I just wanna try it out

I tried to find out but it's not very obvious. It's most likely just checking the phone model name/brand, so you'll need to edit the build.prop to match that of a valid phone (on the supported list of your network).

Also it does a root check that is checking for su app, attempts to do a SU request, looks for su/sudo/busybox, checks if build tags contains test-keys.

freitasm

BDFL - Memuneh
79263 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1278721 7-Apr-2015 23:16

It's a bit more complicated than just checking the manufacturer/model.

eXDee

4032 posts

Uber Geek

Trusted

#1278979 8-Apr-2015 13:07

Xeon:
samo: Can someone tell me how the app is checking the phone model? I just wanna try it out

I tried to find out but it's not very obvious. It's most likely just checking the phone model name/brand, so you'll need to edit the build.prop to match that of a valid phone (on the supported list of your network).

Also it does a root check that is checking for su app, attempts to do a SU request, looks for su/sudo/busybox, checks if build tags contains test-keys.

I can confirm editing the relevant lines in build.prop grants you access to it in the play store, providing you reset all the appropriate data.
The problem is having the SimAlliance API, which will fail the install after download if its missing.

samo

22 posts

Geek

#1279235 8-Apr-2015 19:56

eXDee:
I can confirm editing the relevant lines in build.prop grants you access to it in the play store, providing you reset all the appropriate data.
The problem is having the SimAlliance API, which will fail the install after download if its missing.

Installed from market fine without build.prop edits, app says device is not compatible, although I know it is as it is the same hardware/software as a supported phone and checked SimAlliance API using this app:

https://play.google.com/store/apps/details?id=com.endava.dttest.omapi.check.wallet

Am using rootcloak to hide root access, just need to trick app into thinking my phone is an HTC One not One max

freitasm

BDFL - Memuneh
79263 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1279254 8-Apr-2015 19:58

I just worry about people running this on rooted devices later complaining of strange transactions...

This would probably be the reason for such a restriction, although I wouldn't expect the API to be that easy to exploit - but you never know.

richms

28172 posts

Uber Geek

Trusted

Lifetime subscriber

#1279266 8-Apr-2015 20:13

Surely the whole point of the secure sim hassle is to remove the phone from being vulnerable to having transactions happen like that?

Richard rich.ms

samo

22 posts

Geek

#1279335 8-Apr-2015 21:59

freitasm: I just worry about people running this on rooted devices later complaining of strange transactions...

Having root access and/or sideloading is not of the devil, nor does it make the device less secure, provided you know what your doing.

I wanted to be able to write to my SD card in KitKat, "rooting" is not just used to steal snapchats or install pirated software.

Xeon

302 posts

Ultimate Geek

#1279349 8-Apr-2015 22:11

samo:
freitasm: I just worry about people running this on rooted devices later complaining of strange transactions...

Having root access and/or sideloading is not of the devil, nor does it make the device less secure, provided you know what your doing.

I wanted to be able to write to my SD card in KitKat, "rooting" is not just used to steal snapchats or install pirated software.

"provided you know what your doing", sure for you it doesn't make it less secure but I know people who are really not technically minded with rooted/jailbroken phones. People who write malware probably wouldn't waste their time trying to write 'malware' for such a small userbase though anyway. I presume there is some security which stops other app reading the data semble wrote, right?

1 | ... | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | ... | 17