Help s3 problem with android 4.3 update (EE)

[phil37uk]

Hi all. I have just updated my s3 to 4.3 and whilst I find it's running faster I have a minor glitch which is more an annoyance than anything else. Where the network is displayed across the bottom, it has been replaced with lots od @ signs.

Anyone have/had this problem and how can I get rid of it.

Many thanks in advance.

 

[codesplice]

I've seen this garbled carrier name text (and variations of it) a few times across many devices and carriers, and have never tracked down a common cause. It shouldn't cause any functionality problems; it just looks a bit weird.

A few things that I (and others) have found to help:

- reboot the device
- toggle airplane mode
- toggle APN settings or mobile operator under Settings - Wireless and Networks - More

Hopefully one of these approaches will help you out.

 

[phil37uk]

Cheers, I have tried toggling the flight mode, seems to do the job until I toggle bag and once it finds a signal, reverts back to the @ signs.

 

[Xyro]

I'd be curious to know if there's a solution. I have a S3 on EE in the UK and have been seeing this for a long time now, on various different official and custom roms.

 

[codesplice]

My Google-fu is failing me, and I've only been able to find one other thread discussing a similar garbled carrier string: http://androidforums.com/htc-one/71...ar-shows-00000-where-carrier-name-should.html

By chance, are you also on EE?

Also, are you seeing the same string of symbols on the bottom of the notification pulldown?

 

[phil37uk]

Yeah, I am on EE but it has only been like this since the 4.3 update.

 

[codesplice]

Sounds like it is a known issue with the GS3 4.3 update on EE: http://community.ee.co.uk/t5/Android-Devices/EE-QQQQQQQQQQQQQQQQ/m-p/90676#U90676

Hopefully they can push out a fix before too long, but I'm afraid you're stuck with it until then. At least it's only a cosmetic issue; it won't do any harm other than looking silly.

 

[phil37uk]

That's good to know,many thanks guys.

 

[codesplice]

I went ahead and moved this thread into the Galaxy S3 board so that it can help out others who run into the same issue. :thumbup:

 

[phil37uk]

I went ahead and moved this thread into the Galaxy S3 board so that it can help out others who run into the same issue. :thumbup:

Ahh thanks, just noticed this section after I posted.

 

[phil37uk]

So after a few months this problem still exists, and now found out that we aren't getting the kitkat update, so does anyone know a way to get rid of it, bit of an annoyance more than anything else but, I pay enough to have a good operating phone.

 

[phil37uk]

Think I've sussed it. Not actually the handset's fault or the update as much. I think it is the sim card. I tried my wife's sim in my phone and it went back to normal and mine in hers and the problem showed up on her handset. Same phone same update etc. So I'm gonna request a new sim and take it from there.

 

[phil37uk]

Yeah new sim card sorted it out. Not a fault on the phone!

 

[codesplice]

Glad you got it sorted, and thanks for reporting back! Maybe your experience will be able to help anyone else that runs into the same issue.