Ask / Submit

Revision history [back]

click to hide/show revision 1
initial version

posted 2018-05-25 06:26:06 +0300

three UK SIM no data roaming in Hong Kong

So, I have a ThreeUK SIM card which I'm trying to use in an Xperia X here in Hong Kong. ThreeUK has the Feel-at-home service which allows you to use your UK minutes/SMS and second-class data without incurring costs. You just set your phone to roaming, as normal, and use.

In Android phones, I don't have any issues but with my Xperia, I do. The default APN settings when inserted in the Xperia are the same as in the Android device (APN name three.co.uk etc) but I can't enable data. Voice calls are working just fine.

Has anyone else had similar issues?

three UK SIM no data roaming in Hong Kong

So, I have a ThreeUK SIM card which I'm trying to use in an Xperia X here in Hong Kong. ThreeUK has the Feel-at-home service which allows you to use your UK minutes/SMS and second-class data without incurring costs. You just set your phone to roaming, as normal, and use.

In Android phones, I don't have any issues but with my Xperia, I do. The default APN settings when inserted in the Xperia are the same as in the Android device (APN name three.co.uk etc) but I can't enable data. Voice calls are working just fine.

Has anyone else had similar issues?

EDIT: I also had the same issue with my Nexus4 running the community port but assumed it was specific to that version

three UK SIM no data roaming in Hong Kong

So, I have a ThreeUK SIM card which I'm trying to use in an Xperia X here in Hong Kong. ThreeUK has the Feel-at-home service which allows you to use your UK minutes/SMS and second-class data without incurring costs. You just set your phone to roaming, as normal, and use.

In Android phones, I don't have any issues but with my Xperia, I do. The default APN settings when inserted in the Xperia are the same as in the Android device (APN name three.co.uk etc) but I can't enable data. Voice calls are working just fine.

Has anyone else had similar issues?

EDIT: I also had the same issue with my Nexus4 running the community port but assumed it was specific to that version