Semble SIM: compatible handsets

Forums › Vodafone New Zealand › Semble SIM: compatible handsets

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17

55 posts

Master Geek

# 1281520 12-Apr-2015 16:13

Xeon:
kiwiandy:
Xeon:
kiwiandy: I wonder what else its checking about my HTC in my build.prop that it doesnt like

I would try HTC_0P6B as the model name.

yeah just tried that, same result as when I changed the Android version to 4.4.4 with the Sony Details in build.prop

App starts, and lets me swipe through the intro pages but crashes when i tap new User :(

Is SmartcardService (Openmobileapi) in your list of apps? Sounds like its failing to read/write SE, LogCat logs should give an idea of what went wrong if you are interested.

I am also attempting this with an M8, which has had many different roms etc, and currently is not rooted and running nicely on spark network. Semble app installs and is happy enough except that 'semble is not supported on your phone'.

Build prop says :

ro.product.manufacturer
htc

ro.product.model
htc one_m8

I'm on 5.01, so I wonder if Semble just isn't switched on for M8s with 5.01? Has the OTA for 5.01 come through yet. I know the Semble site says 5.01 is supported, but maybe they'll switch it on when it rolls out OTA.

I'm on Spark, but my CID is Vodap021. Rom is Vietnamese I think? Build prop region says US. Frankenstein phone!

kelly42

20 posts

Geek

# 1281523 12-Apr-2015 16:26

NikT:
markl:
NikT:
Semble won't whitelist a device unless it's certified. Devices can't be certified if we don't have any to give them. If the OnePlus One were to be certified, Semble would need two test units. Give me two OnePlus Ones and I'll ask the question. ;)

Will you give them back again?

Thanks for being up front about everything, btw, it IS appreciated.

Sure! In an ideal world, certification takes around two weeks. I can't guarantee I can get anything certified, as AFAIK we haven't got any commercial agreements in place for handsets that aren't ranged by any telco - they were out of scope of the initial project, and without local vendor support, contacts, or local market software builds, we would have no way of getting any issues that may arise fixed. Semble understandably prefers to hang on to test units in order to ensure the service continues to operate as expected as new software updates roll out. I hope we'll be able to find a happy compromise for all involved in future, it's still early days - and no problem. :)

- Nik

I'm late to this party, but I have a OnePlus One I'd be happy to lend if this would help the certification process! I'm pretty disappointed that I can't hack Semble into working on this unit. I can live with the old Galaxy S4 for a couple of weeks to a month, if I have to, for the betterment of NZ techkind.

ETA: I've just upgraded the OP to OxygenOS so it's running Lollipop; I can downgrade if needed for the cert but I'd hope to blaze some trails with Lollipop support in Semble!

kiwiandy

146 posts

Master Geek

# 1281531 12-Apr-2015 16:42

cebo:
Xeon:
kiwiandy:
Xeon:
kiwiandy: I wonder what else its checking about my HTC in my build.prop that it doesnt like

I would try HTC_0P6B as the model name.

yeah just tried that, same result as when I changed the Android version to 4.4.4 with the Sony Details in build.prop

App starts, and lets me swipe through the intro pages but crashes when i tap new User :(

Is SmartcardService (Openmobileapi) in your list of apps? Sounds like its failing to read/write SE, LogCat logs should give an idea of what went wrong if you are interested.

I am also attempting this with an M8, which has had many different roms etc, and currently is not rooted and running nicely on spark network. Semble app installs and is happy enough except that 'semble is not supported on your phone'.

Build prop says :

ro.product.manufacturer
htc

ro.product.model
htc one_m8

I'm on 5.01, so I wonder if Semble just isn't switched on for M8s with 5.01? Has the OTA for 5.01 come through yet. I know the Semble site says 5.01 is supported, but maybe they'll switch it on when it rolls out OTA.

I'm on Spark, but my CID is Vodap021. Rom is Vietnamese I think? Build prop region says US. Frankenstein phone!

As Xeon advised me, change build.prop to ro.product.model=HTC_0P6B

After I did that the app would load, but crashes when I tap new user at the bottom.

XEON Fyi I do have Smartcard Serice listed in my apps.
Cant check the logcat now as Im flashing a VF NZ Rom to the phone

Xeon

279 posts

Ultimate Geek

# 1281547 12-Apr-2015 17:24

I'm late to this party, but I have a OnePlus One I'd be happy to lend if this would help the certification process! I'm pretty disappointed that I can't hack Semble into working on this unit. I can live with the old Galaxy S4 for a couple of weeks to a month, if I have to, for the betterment of NZ techkind.

ETA: I've just upgraded the OP to OxygenOS so it's running Lollipop; I can downgrade if needed for the cert but I'd hope to blaze some trails with Lollipop support in Semble!

I downloaded OxygenOS but haven't got around to flashing it. Does Oneplus list SmartcardService/Openmobileapi in the Running apps/All installed apps on oxygen?
ColorOS is the only ROM I've found so far with it preinstalled at least, I tried adding the service to CyanogenMod but for reasons beyond my understanding it wasn't working (it couldn't find a method in another file but the references looked fine).

roobarb

483 posts

Ultimate Geek

Trusted

# 1281553 12-Apr-2015 17:44

If you want to confirm that SIMAlliance API is installed correctly on a build then running SnapperMobile with a Touch2Pay SIM will exercise the major functions of locating an applet on the SIM. There is a dependency on protocol the application processor uses to talk to the base-band processor to exchange general purpose APDUs with the SIM ( AT+CSIM/AT+CGLA ).

kelly42

20 posts

Geek

# 1281692 13-Apr-2015 05:09

Xeon: I downloaded OxygenOS but haven't got around to flashing it. Does Oneplus list SmartcardService/Openmobileapi in the Running apps/All installed apps on oxygen?
ColorOS is the only ROM I've found so far with it preinstalled at least, I tried adding the service to CyanogenMod but for reasons beyond my understanding it wasn't working (it couldn't find a method in another file but the references looked fine).

I don't see either of those listed in Runnings apps or All apps, sorry! Anywhere else I should check?

Xeon

279 posts

Ultimate Geek

# 1282018 13-Apr-2015 12:25

kelly42: I don't see either of those listed in Runnings apps or All apps, sorry! Anywhere else I should check?

Nah, it's not on the ROM (wasn't expecting it to be).

Well trying to pay on my OnePlus gives card blocked by the reader for both always on mode and tapping pay on a card in Semble. The Semble app seems to be accessing the SE fine so issue with the NFC I guess.
I suppose this is why they have a phone verification process

ekul

81 posts

Master Geek

# 1284756 15-Apr-2015 14:37

What a pain, I have a M8, was rooted.. Now back on stock with root removed (multiple root checkers confirmed) but Semble says cannot operate on a phone that is rooted.

Does anyone know how vendors(shops etc) treat Semble attached DEBIT cards... It still goes through Visa/Mastercard so does the store have to pay a fee? Will that result in stores passing the 3% charge or whatever it is on to me?

richms

22524 posts

Uber Geek

Trusted

Subscriber

# 1284894 15-Apr-2015 16:22

I have yet to find a store that surcharges that also accepts paywave.

Also for what it's worth of asb have sorted out putting pins on the virtual cards my sim in the note3 that's coming up as rooted will work to buy stuff even with the app not able to run. I can choose semble in the tap and pay list and it will work to buy with the phone locked and screen off. Not tried screen on and stupid me set it to the wrong card when it was in the other phone so can't change that.

So borrow another capable phone, set it up and set a card to always on and it should be good in the "rooted" phone.

Richard rich.ms

Xeon

279 posts

Ultimate Geek

# 1285223 15-Apr-2015 23:18

One person supports this post

Or flash Xposed framework and then use rootcloak

kiwiandy

146 posts

Master Geek

# 1285281 16-Apr-2015 07:22

So I flashed a VF NZ Kit Kat Rom to my Phone... totally amazed that Lollipop is still not available here yet!... (I have been running stock Developer Edition Roms for the last year, which seem to get updates pretty quickly.)

Then I installed RootCloak

Semble starts ok.. get thru to the Profile setup page.. click finish to submit my details..

"Error,, A communication problem occured.... please contact Vodafone. (status 95)

After 40 minutes on the phone, 25 of which were on hold waiting for them to answer... the VF support guy said he didnt have any reference to a status 95 error message.

I dont know when/if i will ever hear back from them.. but I dont really want to face the VF customer service music on hold test again.

sbiddle

28266 posts

Uber Geek

Moderator

Trusted

Biddle Corp

Lifetime subscriber

# 1285298 16-Apr-2015 08:27

kiwiandy: So I flashed a VF NZ Kit Kat Rom to my Phone... totally amazed that Lollipop is still not available here yet!... (I have been running stock Developer Edition Roms for the last year, which seem to get updates pretty quickly.)

Then I installed RootCloak

Semble starts ok.. get thru to the Profile setup page.. click finish to submit my details..

"Error,, A communication problem occured.... please contact Vodafone. (status 95)

After 40 minutes on the phone, 25 of which were on hold waiting for them to answer... the VF support guy said he didnt have any reference to a status 95 error message.

I dont know when/if i will ever hear back from them.. but I dont really want to face the VF customer service music on hold test again.

Why are you expecting Vodafone to provide support for a totally unsupported configuration?

cebo

55 posts

Master Geek

# 1285642 16-Apr-2015 14:43

kiwiandy:
cebo:
Xeon:
kiwiandy:
Xeon:
kiwiandy: I wonder what else its checking about my HTC in my build.prop that it doesnt like

I would try HTC_0P6B as the model name.

yeah just tried that, same result as when I changed the Android version to 4.4.4 with the Sony Details in build.prop

App starts, and lets me swipe through the intro pages but crashes when i tap new User :(

Is SmartcardService (Openmobileapi) in your list of apps? Sounds like its failing to read/write SE, LogCat logs should give an idea of what went wrong if you are interested.

I am also attempting this with an M8, which has had many different roms etc, and currently is not rooted and running nicely on spark network. Semble app installs and is happy enough except that 'semble is not supported on your phone'.

Build prop says :

ro.product.manufacturer
htc

ro.product.model
htc one_m8

I'm on 5.01, so I wonder if Semble just isn't switched on for M8s with 5.01? Has the OTA for 5.01 come through yet. I know the Semble site says 5.01 is supported, but maybe they'll switch it on when it rolls out OTA.

I'm on Spark, but my CID is Vodap021. Rom is Vietnamese I think? Build prop region says US. Frankenstein phone!

As Xeon advised me, change build.prop to ro.product.model=HTC_0P6B

After I did that the app would load, but crashes when I tap new user at the bottom.

XEON Fyi I do have Smartcard Serice listed in my apps.
Cant check the logcat now as Im flashing a VF NZ Rom to the phone

So, after finally working out how to change the build prop on a non-rooted phone (which turns out to be adb, twrp and s-off), and getting my Semble sim activated - which wasn't smooth sailing - the Semble app, launched without any grumbling and I set up an account and loaded a card. Off to New World for a test.

"Too many cards please try again", "too many cards please try again", "unable to read card". Sigh. Still, this process has taught me a whole bunch about how my phone works, even if that wasn't the point to start with.

roobarb

483 posts

Ultimate Geek

Trusted

# 1285664 16-Apr-2015 15:18

cebo:"Too many cards please try again", "too many cards please try again", "unable to read card".

This is likely to be at the RF level between the reader and the handset, where the reader cannot establish a reliable RF session with the phone. Try holding the phone at different distances away from the reader. (eg 0mm, 5mm, 10mm, 20mm) and hold it steady. You can try holding the handset so that you can use your finger pads act as a spacer.

richms

22524 posts

Uber Geek

Trusted

Subscriber

# 1285704 16-Apr-2015 16:19

I have had that on my phone when it was in the process of turning the screen off because of the smart cover being closed and then me placing it on the reader.

Ive found I have to have it either opened up with the semble app showing, or locked and screen off for it to transact ok.

Richard rich.ms

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17