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

750 posts

Ultimate Geek
+1 received by user: 342

Trusted

Reply # 1280306 10-Apr-2015 10:29

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 ?

Hi KD66

The telco companies (so Vodafone, Spark, 2degrees) can request Semble approve particular phones. This is done by one of us sending them two of the phones for them to throughly test the Semble app on and make sure it passes all the necessary approvals. Remember we're talking about integrating with banks, credit cards and payments so I'm guessing it's quite strict.

After a device is approved by Semble the approval can be made available to all three versions of the Semble app (there's different versions of the app for each of the telcos). I'm not sure if that particular phone has been submitted for approval. If it hasn't been yet it still could be.

Dylan

Handsomedan

1954 posts

Uber Geek
+1 received by user: 406

Subscriber

Reply # 1280324 10-Apr-2015 10:48

markl:
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.

IMHO, AIANAL, YMMV.

FTW!

Handsome Dan Has Spoken.

kiwiandy

144 posts

Master Geek
+1 received by user: 11

Reply # 1280398 10-Apr-2015 12:31

Can anyone tell me what the Rom version is thats in the VFNZ version of the M8

Mine is an unlocked developer edition, and guess I need to flash the VFNZ rom to make this work?

qyiet

454 posts

Ultimate Geek
+1 received by user: 95

Trusted

Reply # 1280487 10-Apr-2015 13:57

One person supports this post

Handsomedan:

IMHO, AIANAL, YMMV.

FTW!

I take it the new rule is that we must include a TLA or longer in any post.

Warning: reality may differ from above post

roobarb

483 posts

Ultimate Geek
+1 received by user: 286

Trusted

Reply # 1280623 10-Apr-2015 17:42

markl: It's even worse, in my opinion...

All I said to my wife was that piece of halibut was good enough for Jehovah.

http://en.wikipedia.org/wiki/Mobile_network_operator
http://en.wikipedia.org/wiki/Original_equipment_manufacturer

KD66

12 posts

Geek
+1 received by user: 1

Reply # 1281236 11-Apr-2015 21:31

One person supports this post

VodafoneDylan:
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 ?

Hi KD66

The telco companies (so Vodafone, Spark, 2degrees) can request Semble approve particular phones. This is done by one of us sending them two of the phones for them to throughly test the Semble app on and make sure it passes all the necessary approvals. Remember we're talking about integrating with banks, credit cards and payments so I'm guessing it's quite strict.

After a device is approved by Semble the approval can be made available to all three versions of the Semble app (there's different versions of the app for each of the telcos). I'm not sure if that particular phone has been submitted for approval. If it hasn't been yet it still could be.

Dylan

Thanks Dylan

Xeon

279 posts

Ultimate Geek
+1 received by user: 39

Reply # 1281298 12-Apr-2015 00:06

Well, changed to ColorOS rom on my Oneplus which includes OpenMobileApi at stock. Then using rootcloak and changing the build.prop (Model/Manufacturer) to match a valid model I can use the Semble app fine. The log was showing it was reading the SE fine and scanning my phone with another phone showed it as a Visa Smartcard so looks positive at least.

Not in the city at the moment so no idea if it will actually pay properly however. Will give it a test tomorrow (or the next day).

samo

22 posts

Geek

Reply # 1281299 12-Apr-2015 00:10

Xeon: Well, changed to ColorOS rom on my Oneplus which includes OpenMobileApi at stock. Then using rootcloak and changing the build.prop (Model/Manufacturer) to match a valid model I can use the Semble app fine.

Can you share your build.prop changes?

Xeon

279 posts

Ultimate Geek
+1 received by user: 39

Reply # 1281300 12-Apr-2015 00:18

One person supports this post

samo: Can you share your build.prop changes?

/system/build.prop:

ro.product.model=D6653
ro.product.manufacturer=Sony

Where Sony/D6653 is any valid devices details for the relevant network.
(Edit this file at your own risk)

kiwiandy

144 posts

Master Geek
+1 received by user: 11

Reply # 1281403 12-Apr-2015 12:43

kiwiandy:
Xeon:
samo: Can you share your build.prop changes?

/system/build.prop:

ro.product.model=D6653
ro.product.manufacturer=Sony

Where Sony/D6653 is any valid devices details for the relevant network.
(Edit this file at your own risk)

I have an HTC one M8 Developer edition, and checking the build.prop the entries are the same as shown on the semble website
So I guess they are looking at another entry on the M8. I have tried changing the CID to VODAP022 but still doesnt work.
Can anyone send me the build.prop file for a VFNZ HTC one M8 please?

Xeon

279 posts

Ultimate Geek
+1 received by user: 39

Reply # 1281414 12-Apr-2015 13:00

kiwiandy:
kiwiandy:
Xeon:
samo: Can you share your build.prop changes?

/system/build.prop:

ro.product.model=D6653
ro.product.manufacturer=Sony

Where Sony/D6653 is any valid devices details for the relevant network.
(Edit this file at your own risk)

I have an HTC one M8 Developer edition, and checking the build.prop the entries are the same as shown on the semble website
So I guess they are looking at another entry on the M8. I have tried changing the CID to VODAP022 but still doesnt work.
Can anyone send me the build.prop file for a VFNZ HTC one M8 please?

Is it on 4.4.4/5.0.1?
The only device type checks I can see are: Root check, android version, manufacturer, model. It gives you device not supported error correct?

kiwiandy

144 posts

Master Geek
+1 received by user: 11

Reply # 1281463 12-Apr-2015 14:34

Xeon:
kiwiandy:
kiwiandy:
Xeon:
samo: Can you share your build.prop changes?

/system/build.prop:

ro.product.model=D6653
ro.product.manufacturer=Sony

Where Sony/D6653 is any valid devices details for the relevant network.
(Edit this file at your own risk)

I have an HTC one M8 Developer edition, and checking the build.prop the entries are the same as shown on the semble website
So I guess they are looking at another entry on the M8. I have tried changing the CID to VODAP022 but still doesnt work.
Can anyone send me the build.prop file for a VFNZ HTC one M8 please?

Is it on 4.4.4/5.0.1?
The only device type checks I can see are: Root check, android version, manufacturer, model. It gives you device not supported error correct?

Its on 5.01

Yes correct it gives a this phone is not supported status 15 error
my build.prop shows
ro.product.model=HTC One_M8
ro.product.manufacturer=HTC

which agrees with what is shown on the Semble website :
HTC Supported OS HTC One M8 [HTC_0P6B] 4.4.4, 5.0.1

HTC_0P6B is a different entry in the build.prop
ro.aa.modelid=0P6B12000 , 0P6B13000

Just for interest I changed my buid.prop as per yours:
ro.product.model=D6653
ro.product.manufacturer=Sony

Now it aborts with an error saying that my current OS is not supported, (status 78) so I guess it now believes I have a Sony, but doesn't like 5.01 running on the Sony!

So next step is to change the android version in build.prop to 4.4.4
App now starts, and can swipe through the introductory pages, but crashes when i try to register new user :(

Xeon

279 posts

Ultimate Geek
+1 received by user: 39

Reply # 1281478 12-Apr-2015 15:16

One person supports this post

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.

kiwiandy

144 posts

Master Geek
+1 received by user: 11

Reply # 1281507 12-Apr-2015 15:44

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 :(

Xeon

279 posts

Ultimate Geek
+1 received by user: 39

Reply # 1281516 12-Apr-2015 15:58

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.

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