We have moved to a new Sailfish OS Forum. Please start new discussions there.
13

USSD codes not working

Tracked by Jolla

asked 2020-01-11 09:57:40 +0300

Dreej gravatar image

updated 2020-01-13 08:28:35 +0300

Edit:

image description

I always get this notifocation..

Hi guys,

I'm here in the Philippines and I noticed that USSD codes are not working. I can't load nor check my balance nor any other option. I never had to use it before in Germany but I know it worked with an oder OS version. The one from June 2019 :) Is it a problem with the OS or the provider here? I have a XA2 Plus dual sim running 3.2.1.20

has anyone a solution?

edit retag flag offensive close delete

Comments

I have same issue, here in Malaysia.

bane07 ( 2020-02-03 20:42:09 +0300 )edit

5 Answers

Sort by » oldest newest most voted
2

answered 2020-01-11 10:12:06 +0300

Maus gravatar image

USSD requests work well here (on JP1301 with SFOS 3.2.1.20). I can only guess that you are still using your German SIM and USSD requests are not proxied. If you use a SIM from a local M(V)NO, this would be a different case.

edit flag offensive delete publish link more

Comments

3

i concur with the original poster ever since 3.2 i cannot properly use the ussd codes, it only returns a response the first time but after that it states the operation is busy and i get stuck, i plan to downgrade if this isnt fixed

ubuntuscofield ( 2020-01-12 14:08:45 +0300 )edit

No problem here with a Jolla1 on 3.2.1.20 (in Germany, Telekom network).

Holger ( 2020-01-12 15:56:40 +0300 )edit
1

On a J1 (JP1301), I just sent three successive USSD requests and all of them were answered OK.

Maus ( 2020-01-12 17:14:02 +0300 )edit

so it seems to be a problem with the XA2.

And no, I have set everything to my local SIM. even deactivating my German SIM card solves the problem

Dreej ( 2020-01-13 08:23:59 +0300 )edit
1

I have the same problem as described by original poster, Jolla1 on 3.2.1.20. It was working fine on the previous versions of SFOS.

Nova ( 2020-01-13 14:07:24 +0300 )edit
2

answered 2020-02-02 13:30:15 +0300

cy8aer gravatar image

Error occurs on german o2 with *100#

edit flag offensive delete publish link more
2

answered 2020-02-04 10:25:54 +0300

ubuntuscofield gravatar image

updated 2020-02-04 17:20:31 +0300

s_mario gravatar image

Here is a workaround, once you get to that response you wait until it changes to problem with service request then you can input and get the desired response.

edit flag offensive delete publish link more
1

answered 2020-05-02 19:01:04 +0300

dumol gravatar image

updated 2020-05-02 19:04:25 +0300

Another workaround is to send the complete sequence of codes from the start.

For example, for me *110# is the relevant initiation sequence, then i would like to choose 4 and then 1 to check validity. Complete sequence to be called at once would be *110*4*1#.

By chance, I had such a complete sequence saved in the address book since using a Nokia N9. ;-]

edit flag offensive delete publish link more
0

answered 2020-01-13 14:11:32 +0300

AkiBerlin gravatar image

updated 2020-01-13 17:10:08 +0300

Just checked the *#06# USSD request (IMEI) on my Xperia XA2 non-+ dual SIM with Deutsche Telekom and on my Xperia 10 non-+ dual SIM with Vodaphone.

Both requests were fine.

Could it be a problem of the provider in the Philippines?

EDIT:

I tried further codes and some caused a reboot of the Xperia 10 So it might well be a problem of SFOS

edit flag offensive delete publish link more

Comments

3

The issue isnt with one time response ussd codes, like requesting for balance or checking imei but rather if one request services that require several responses in the ussd window. It seems after running the ussd code, the pop up that returns is okay but if you try entering feedback or responding to it, lets say choose 1 for this or 2 for this it doesn't work, from my tinkering i have to wait until an argument is not recognized feedback then i can continue without hiccups.

ubuntuscofield ( 2020-01-13 14:19:30 +0300 )edit

I undersood that Dreej cannot even check the balance. From what I understood, USSD cods in general are not working with him

AkiBerlin ( 2020-01-13 15:26:58 +0300 )edit
1

I don't think it's a prob with the provider. as I stated it worked before.

it's like ubuntuscofield stated. I can open the menu by*142# after I can type for example a 2 for my account and after I get the screenshot I sent. plus the phone falls down from 4G to 3G for some mins

Dreej ( 2020-01-13 15:52:54 +0300 )edit

@Dreej, would you please update your question with what you found out meanwhile, adapting the title a bit?

Maus ( 2020-01-13 17:48:16 +0300 )edit
Login/Signup to Answer

Question tools

Follow
4 followers

Stats

Asked: 2020-01-11 09:57:40 +0300

Seen: 1,112 times

Last updated: Jun 01 '20