Semble SIM: compatible handsets

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

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

BDFL - Memuneh
79608 posts

Uber Geek
+1 received by user: 38034

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1279395 9-Apr-2015 05:41

The same way Windows users run Administrator accounts. They know what they are doing my, surely?

My point is that there will be those who have no clue.

Please support Geekzone by subscribing, or using one of our referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Geekzone and Quic social @ DataVault Auckland 18 Oct 2025 11AM - 2:30 PM

DrDee

269 posts

Ultimate Geek
+1 received by user: 45

#1279526 9-Apr-2015 10:50

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

This is the retarded bit, if you have the gumption to root then xposed/root-cloak is a simple solution. Makes you wonder why they bother. A couple of games I play introduced checking for modified device, even on the app store webpage the reviewers just mention to use root-cloak if you are rooted to pass the check.

Surely build.prop (ro.product.model=xxx) is all you need to do, works with other incompatible apps on the play store.

For me the phone model is compatible, the Android version is not, might go and see if I can get it installed with a build.prop change.

KD66

12 posts

Geek
+1 received by user: 1

#1279997 9-Apr-2015 20:35

I have a Galaxy Core Prime handset which runs on Android 4.4.4 and has NFC. Yet it is not listed as a compatible handset. Anyone knows why ?

freitasm

BDFL - Memuneh
79608 posts

Uber Geek
+1 received by user: 38034

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1279998 9-Apr-2015 20:37

Was this handset ever available through NZ mobile operators? If not, then it was not tested.

Please support Geekzone by subscribing, or using one of our referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Geekzone and Quic social @ DataVault Auckland 18 Oct 2025 11AM - 2:30 PM

KD66

12 posts

Geek
+1 received by user: 1

#1280002 9-Apr-2015 20:42

freitasm: Was this handset ever available through NZ mobile operators? If not, then it was not tested.

Umm, I have got this from Vodafone here in Auckland...

roobarb

653 posts

Ultimate Geek
+1 received by user: 508

Trusted

#1280011 9-Apr-2015 20:51

KD66: I have a Galaxy Core Prime handset which runs on Android 4.4.4 and has NFC. Yet it is not listed as a compatible handset. Anyone knows why ?

Handset firmware needs to have SIM Alliance API installed by the OEM. This needs to be requested as a feature by the MNO for each specific model they order, it is not a component provided by Google.

With Semble we should see this as a standard feature on hardware capable NFC handsets as each NZ MNO will be wanting it.

KD66

12 posts

Geek
+1 received by user: 1

#1280041 9-Apr-2015 21:32

roobarb:
KD66: I have a Galaxy Core Prime handset which runs on Android 4.4.4 and has NFC. Yet it is not listed as a compatible handset. Anyone knows why ?

Handset firmware needs to have SIM Alliance API installed by the OEM. This needs to be requested as a feature by the MNO for each specific model they order, it is not a component provided by Google.

With Semble we should see this as a standard feature on hardware capable NFC handsets as each NZ MNO will be wanting it.

So I am reading from your comment that the API is not installed in the Galaxy Core Prime. Sorry I feel like a bumbling idiot but most of the abbreviations you have used are beyond me.

Sharesies

Trade NZ and US shares and funds with Sharesies (affiliate link).

Xeon

302 posts

Ultimate Geek
+1 received by user: 43

#1280045 9-Apr-2015 21:43

KD66:
roobarb:
KD66: I have a Galaxy Core Prime handset which runs on Android 4.4.4 and has NFC. Yet it is not listed as a compatible handset. Anyone knows why ?

Handset firmware needs to have SIM Alliance API installed by the OEM. This needs to be requested as a feature by the MNO for each specific model they order, it is not a component provided by Google.

With Semble we should see this as a standard feature on hardware capable NFC handsets as each NZ MNO will be wanting it.

So I am reading from your comment that the API is not installed in the Galaxy Core Prime. Sorry I feel like a bumbling idiot but most of the abbreviations you have used are beyond me.

Go to Settings -> Apps -> Running/All and look for 'SmartcardService'.

That will tell you if it has the API BUT even if it does have the API you'll need Semble to approve the phone before the app will function on the phone.

KD66

12 posts

Geek
+1 received by user: 1

#1280058 9-Apr-2015 21:57

Xeon:
KD66:
roobarb:
KD66: I have a Galaxy Core Prime handset which runs on Android 4.4.4 and has NFC. Yet it is not listed as a compatible handset. Anyone knows why ?

Handset firmware needs to have SIM Alliance API installed by the OEM. This needs to be requested as a feature by the MNO for each specific model they order, it is not a component provided by Google.

With Semble we should see this as a standard feature on hardware capable NFC handsets as each NZ MNO will be wanting it.

So I am reading from your comment that the API is not installed in the Galaxy Core Prime. Sorry I feel like a bumbling idiot but most of the abbreviations you have used are beyond me.

Go to Settings -> Apps -> Running/All and look for 'SmartcardService'.

That will tell you if it has the API BUT even if it does have the API you'll need Semble to approve the phone before the app will function on the phone.

Thanks for explaining, and yes it does have SmartcardService. So I guess I will have to contact Semble in some way to see if I can request them to approve this handset .

samo

22 posts

Geek

#1280247 10-Apr-2015 09:37

OK so I have got it work, well partly, I set it up in my wifes S5 then switched the sim back in my HTC One max and as long as "always on" was chosen i can make a payment using the HTC. Still cant open the app even though I can set it as a payment method in the settings.

On rooted handsets: I had a look at their code and they are checking for su,sudo,busybox,SuperUser.apk, all of which are hidden using rootcloak, as I can get past the root check but not phone model.

My guess is they are referring to the IMEI number to get the phone model, maybe even server side using your provider, because I can't find the check in their code, If thats the case I'm stuck. I could have missed it though.

Just glad I can use it =)

markl

348 posts

Ultimate Geek
+1 received by user: 83

#1280255 10-Apr-2015 09:44

KD66:
roobarb:
KD66: I have a Galaxy Core Prime handset which runs on Android 4.4.4 and has NFC. Yet it is not listed as a compatible handset. Anyone knows why ?

Handset firmware needs to have SIM Alliance API installed by the OEM. This needs to be requested as a feature by the MNO for each specific model they order, it is not a component provided by Google.

With Semble we should see this as a standard feature on hardware capable NFC handsets as each NZ MNO will be wanting it.

So I am reading from your comment that the API is not installed in the Galaxy Core Prime. Sorry I feel like a bumbling idiot but most of the abbreviations you have used are beyond me.

<warning: somewhat passive-aggressive, off-topic, rant coming up>

Don't feel bad - there are certain (senior, in some cases) forum members who seem to delight in using obtuse and esoteric technical language and acronyms for things that are mundane, in an attempt to appear somehow superior to everyone else. All it does is mean that anyone who hasn't seen that acronym before has to work harder to understand what they're on about.

Personally I read that acronym as "carrier" - so I'm guessing that Roobarb's use of MNO should be interpreted as "Mobile Network Operator"? As I say, it's just a means to make them feel like their knowledge is superior to that of everyone else.

freitasm

BDFL - Memuneh
79608 posts

Uber Geek
+1 received by user: 38034

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1280263 10-Apr-2015 09:51

samo: OK so I have got it work, well partly, I set it up in my wifes S5 then switched the sim back in my HTC One max and as long as "always on" was chosen i can make a payment using the HTC. Still cant open the app even though I can set it as a payment method in the settings.

Yes, this is the same method I used on my HTC One M9 - enabled on M8, set a default card always on and moved the SIM. This also works for Windows Phone and BlackBerry 10.

Now that the M9 is available through retail I guess Semble will work to fix the "identification" problem they found with it. Shame they knew the handset was coming and could have that fixed for release date if they could just extend a hand to HTC/operators and asked...

Please support Geekzone by subscribing, or using one of our referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Geekzone and Quic social @ DataVault Auckland 18 Oct 2025 11AM - 2:30 PM

freitasm

BDFL - Memuneh
79608 posts

Uber Geek
+1 received by user: 38034

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1280264 10-Apr-2015 09:52

markl:
KD66:
roobarb:
KD66: I have a Galaxy Core Prime handset which runs on Android 4.4.4 and has NFC. Yet it is not listed as a compatible handset. Anyone knows why ?

Handset firmware needs to have SIM Alliance API installed by the OEM. This needs to be requested as a feature by the MNO for each specific model they order, it is not a component provided by Google.

With Semble we should see this as a standard feature on hardware capable NFC handsets as each NZ MNO will be wanting it.

So I am reading from your comment that the API is not installed in the Galaxy Core Prime. Sorry I feel like a bumbling idiot but most of the abbreviations you have used are beyond me.

<warning: somewhat passive-aggressive, off-topic, rant coming up>

Don't feel bad - there are certain (senior, in some cases) forum members who seem to delight in using obtuse and esoteric technical language and acronyms for things that are mundane, in an attempt to appear somehow superior to everyone else. All it does is mean that anyone who hasn't seen that acronym before has to work harder to understand what they're on about.

Personally I read that acronym as "carrier" - so I'm guessing that Roobarb's use of MNO should be interpreted as "Mobile Network Operator"? As I say, it's just a means to make them feel like their knowledge is superior to that of everyone else.

I don't think people hide behind acronyms to appear superior. It's just that some people work in the industry and are used to these in their day-to-day. It's an automatic thing.

I don't subscribe to your conspiracy theory :)

Please support Geekzone by subscribing, or using one of our referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Geekzone and Quic social @ DataVault Auckland 18 Oct 2025 11AM - 2:30 PM

samo

22 posts

Geek

#1280269 10-Apr-2015 10:02

freitasm: Yes, this is the same method I used on my HTC One M9...

Jealous.

markl

348 posts

Ultimate Geek
+1 received by user: 83

#1280270 10-Apr-2015 10:04

freitasm:

I don't think people hide behind acronyms to appear superior. It's just that some people work in the industry and are used to these in their day-to-day. It's an automatic thing.

I don't subscribe to your conspiracy theory :)

Heh...conspiracy theory :)

No, I get that acronyms are necessary in some circumstances, however I do feel that often people use them unnecessarily - and the same goes for other overly technical jargon. It's one thing when you're geeking out with a bunch of other nerds, hell I do it all the time in that circumstance myself. But when you're in conversation with less technical people then you really have to question it. All you're doing is failing to get your message across effectively to your audience, who are likely just nodding politely because they're afraid to ask you to explain what you mean.

It's even worse, in my opinion, when it happens in an online discussion, as you have the time to explain, or type out an alternative. Take this example. Poor KD66 admitted to not understanding. This would have taken Roobarb only an extra, maybe, 20 characters of typing to remove both of the acronyms used? And the message would have been perfectly clear.

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