From Newsgroup: uk.telecom.mobile

We have an ancient (12 years old) Samsung E1195 clamshell "feature"
phone. It's really only used these days for receiving the odd text
message, mainly those with a 6-number code for 2FA.

The phone is on a very old Vodafone PAYG contract, and I don't think
it's been topped up for years. Vodafone sent a text last week to say if
it wasn't used in the next 90 days the number would be forfeit. I've got
round this before by sending a short text from it to my phone. This
time, though, sending a text failed. There was a "spinner" on the screen
for about 10 seconds. Then the screen went black, and after about 5
seconds it showed "Error", and asked if I wanted to retry or exit. Retry
just did the same thing. It still receives texts, and can make and
receive calls.

I couldn't work out what was going on, but wondered if, following the
Vodafone text, the Voda service was somehow stopping the texts. So I
went to the local Vodafone shop today to ask them if they had any ideas.
The guy there was as puzzled as I am - neither of us knew the phone was
even capable of displaying "Error". He confirmed it wasn't the Voda
service blocking the texts. In the end we agreed that it was probably
the phone which was faulty, and also agreed that it made sense for me to
just transfer the 2FA text confirmation to my phone number.

By the way, there was nothing of help in the E1195 service manual which
I downloaded from Elektrotanya.
--
Jeff

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

Jeff Layman <Jeff@invalid.invalid> writes:

We have an ancient (12 years old) Samsung E1195 clamshell "feature"
phone. It's really only used these days for receiving the odd text
message, mainly those with a 6-number code for 2FA.

The phone is on a very old Vodafone PAYG contract, and I don't think
it's been topped up for years. Vodafone sent a text last week to say
if it wasn't used in the next 90 days the number would be
forfeit. I've got round this before by sending a short text from it to
my phone. This time, though, sending a text failed. There was a
"spinner" on the screen for about 10 seconds. Then the screen went
black, and after about 5 seconds it showed "Error", and asked if I
wanted to retry or exit. Retry just did the same thing. It still
receives texts, and can make and receive calls.

I couldn't work out what was going on, but wondered if, following the Vodafone text, the Voda service was somehow stopping the texts. So I
went to the local Vodafone shop today to ask them if they had any
ideas. The guy there was as puzzled as I am - neither of us knew the
phone was even capable of displaying "Error". He confirmed it wasn't
the Voda service blocking the texts. In the end we agreed that it was probably the phone which was faulty, and also agreed that it made
sense for me to just transfer the 2FA text confirmation to my phone
number.

By the way, there was nothing of help in the E1195 service manual
which I downloaded from Elektrotanya.

My old nokia phone started doing strange things after it had been left
on for a very long time, so I did something like switch it off and on,
or took the battery out and put it back in and it was OK afterwards.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

On Mon, 21 Jul 2025 17:08:15 +0100, Jeff Layman <Jeff@invalid.invalid>
wrote:

We have an ancient (12 years old) Samsung E1195 clamshell "feature"
phone. It's really only used these days for receiving the odd text
message, mainly those with a 6-number code for 2FA.

The phone is on a very old Vodafone PAYG contract, and I don't think
it's been topped up for years. Vodafone sent a text last week to say if
it wasn't used in the next 90 days the number would be forfeit. I've got >round this before by sending a short text from it to my phone. This
time, though, sending a text failed. There was a "spinner" on the screen
for about 10 seconds. Then the screen went black, and after about 5
seconds it showed "Error", and asked if I wanted to retry or exit. Retry >just did the same thing. It still receives texts, and can make and
receive calls.

If the only stipulation is that you have to 'use' the phone, surely
making a call would be sufficient? Why do you need to send a text?
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

On Mon, 21 Jul 2025 17:08:15 +0100, Jeff Layman wrote:

We have an ancient (12 years old) Samsung E1195 clamshell "feature"
phone. It's really only used these days for receiving the odd text
message, mainly those with a 6-number code for 2FA.

The phone is on a very old Vodafone PAYG contract, and I don't think
it's been topped up for years. Vodafone sent a text last week to say if
it wasn't used in the next 90 days the number would be forfeit. I've got round this before by sending a short text from it to my phone. This
time, though, sending a text failed. There was a "spinner" on the screen
for about 10 seconds. Then the screen went black, and after about 5
seconds it showed "Error", and asked if I wanted to retry or exit. Retry
just did the same thing. It still receives texts, and can make and
receive calls.

I couldn't work out what was going on, but wondered if, following the Vodafone text, the Voda service was somehow stopping the texts. So I
went to the local Vodafone shop today to ask them if they had any ideas.
The guy there was as puzzled as I am - neither of us knew the phone was
even capable of displaying "Error". He confirmed it wasn't the Voda
service blocking the texts. In the end we agreed that it was probably
the phone which was faulty, and also agreed that it made sense for me to
just transfer the 2FA text confirmation to my phone number.

By the way, there was nothing of help in the E1195 service manual which
I downloaded from Elektrotanya.

I assume you checked the credit.

When I changed my main phone number a year or so back it was a PITA
changing the F2A numbers. Every bank and Savings organisation had a
different Procedure. Only one allowed me to do it online, I think, most required me to ring up.

I changed as many as possible to use an authenticator app, but no banks
etc. allowed that. But PayPal and all my email accounts do.

It might be easier to just get another old phone. I have a drawer-full of
old Nokias: I expect lots of people do.
--
(Remove any numerics from my email address.)
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

On Mon 21/07/2025 17:36, Scott wrote:

On Mon, 21 Jul 2025 17:08:15 +0100, Jeff Layman <Jeff@invalid.invalid>
wrote:

We have an ancient (12 years old) Samsung E1195 clamshell "feature"
phone. It's really only used these days for receiving the odd text
message, mainly those with a 6-number code for 2FA.

The phone is on a very old Vodafone PAYG contract, and I don't think
it's been topped up for years. Vodafone sent a text last week to say if
it wasn't used in the next 90 days the number would be forfeit. I've got
round this before by sending a short text from it to my phone. This
time, though, sending a text failed. There was a "spinner" on the screen
for about 10 seconds. Then the screen went black, and after about 5
seconds it showed "Error", and asked if I wanted to retry or exit. Retry
just did the same thing. It still receives texts, and can make and
receive calls.

If the only stipulation is that you have to 'use' the phone, surely
making a call would be sufficient? Why do you need to send a text?

The phone is on PAYG so a text message is cheaper than a call.

Simples?
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

On 21/07/2025 17:08, Jeff Layman wrote:

We have an ancient (12 years old) Samsung E1195 clamshell "feature"
phone. It's really only used these days for receiving the odd text
message, mainly those with a 6-number code for 2FA.

The phone is on a very old Vodafone PAYG contract, and I don't think
it's been topped up for years. Vodafone sent a text last week to say if
it wasn't used in the next 90 days the number would be forfeit. I've got round this before by sending a short text from it to my phone. This
time, though, sending a text failed. There was a "spinner" on the screen
for about 10 seconds. Then the screen went black, and after about 5
seconds it showed "Error", and asked if I wanted to retry or exit. Retry
just did the same thing. It still receives texts, and can make and
receive calls.

I couldn't work out what was going on, but wondered if, following the Vodafone text, the Voda service was somehow stopping the texts. So I
went to the local Vodafone shop today to ask them if they had any ideas.
The guy there was as puzzled as I am - neither of us knew the phone was
even capable of displaying "Error". He confirmed it wasn't the Voda
service blocking the texts. In the end we agreed that it was probably
the phone which was faulty, and also agreed that it made sense for me to
just transfer the 2FA text confirmation to my phone number.

By the way, there was nothing of help in the E1195 service manual which
I downloaded from Elektrotanya.

Thanks for the replies.

One of the first things I did was remove the battery and sim and clean
the contacts before replacing. It made no difference.

I did try to make a call and it worked, but that was after trying to
send a text (as noted it is cheaper). I thought I'd post here because
the fault was unusual - but perhaps not so unusual as seeing an error
message on a feature phone! There is plenty of credit - over -u5 when I checked.

From what I remember, there are only three or four accounts which use
2FA with the phone, so changing to a different phone number shouldn't be
too difficult. I'd forgotten about the possibility of using an old phone
by moving the sim to it. Until about 6 months ago I had kept an old
Samsung GT-B3210 for at least 10 years, but one day decided it would
have to go - isn't that typical?! Then I remembered I had an old Huawei
Y300 smartphone; I'm trying to charge it up now to see how it behaves.
If it keeps its charge for more than 72 hours I'll move the sim into it
and see if it can send a text.
--
Jeff
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

Jeff Layman <Jeff@invalid.invalid> wrote:

We have an ancient (12 years old) Samsung E1195 clamshell "feature"
phone. It's really only used these days for receiving the odd text
message, mainly those with a 6-number code for 2FA.

The phone is on a very old Vodafone PAYG contract, and I don't think
it's been topped up for years. Vodafone sent a text last week to say if
it wasn't used in the next 90 days the number would be forfeit. I've got round this before by sending a short text from it to my phone. This
time, though, sending a text failed. There was a "spinner" on the screen
for about 10 seconds. Then the screen went black, and after about 5
seconds it showed "Error", and asked if I wanted to retry or exit. Retry just did the same thing. It still receives texts, and can make and
receive calls.

I couldn't work out what was going on, but wondered if, following the Vodafone text, the Voda service was somehow stopping the texts. So I
went to the local Vodafone shop today to ask them if they had any ideas.
The guy there was as puzzled as I am - neither of us knew the phone was
even capable of displaying "Error". He confirmed it wasn't the Voda
service blocking the texts. In the end we agreed that it was probably
the phone which was faulty, and also agreed that it made sense for me to just transfer the 2FA text confirmation to my phone number.

On traditional phones you needed to have the number of the SMSC in settings
to be able to send SMS. Typically this came from the SIM card.

Not sure how it works on modern phones, but perhaps in all the networks'
focus on whizzy 5Gness the phone has forgotten the SMSC setting?

Theo
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

On 23/07/2025 10:23, Theo wrote:

Jeff Layman <Jeff@invalid.invalid> wrote:

We have an ancient (12 years old) Samsung E1195 clamshell "feature"
phone. It's really only used these days for receiving the odd text
message, mainly those with a 6-number code for 2FA.

The phone is on a very old Vodafone PAYG contract, and I don't think
it's been topped up for years. Vodafone sent a text last week to say if
it wasn't used in the next 90 days the number would be forfeit. I've got
round this before by sending a short text from it to my phone. This
time, though, sending a text failed. There was a "spinner" on the screen
for about 10 seconds. Then the screen went black, and after about 5
seconds it showed "Error", and asked if I wanted to retry or exit. Retry
just did the same thing. It still receives texts, and can make and
receive calls.

I couldn't work out what was going on, but wondered if, following the
Vodafone text, the Voda service was somehow stopping the texts. So I
went to the local Vodafone shop today to ask them if they had any ideas.
The guy there was as puzzled as I am - neither of us knew the phone was
even capable of displaying "Error". He confirmed it wasn't the Voda
service blocking the texts. In the end we agreed that it was probably
the phone which was faulty, and also agreed that it made sense for me to
just transfer the 2FA text confirmation to my phone number.

On traditional phones you needed to have the number of the SMSC in settings to be able to send SMS. Typically this came from the SIM card.

Not sure how it works on modern phones, but perhaps in all the networks' focus on whizzy 5Gness the phone has forgotten the SMSC setting?

I hadn't heard of the SMSC number, but my first thought was why can the
phone receive texts? If there was a problem with the SMSC, wouldn't it
neither send nor receive texts?

Anyway, further to my reply above, I put the sim in the Huawei and tried
to send a text. It failed again, and I got a text from Vodafone
(automatic reply?) with something relating to using a phone with updated software or it needing a new APN, and reference to a Vodafone webpage.
The webpage was of no use.

I played around a bit more and found the Huawei behaved exactly the same
as the Samsung. It could receive texts, and make and receive phone calls
only - it could not send a text. I assume the sim is faulty.
--
Jeff
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

Jeff Layman <Jeff@invalid.invalid> wrote:

I hadn't heard of the SMSC number, but my first thought was why can the phone receive texts? If there was a problem with the SMSC, wouldn't it neither send nor receive texts?

"If you canrCOt send, but only receive, text messages, you might need to set the SMS service center number (SMSC) manually. The SMS service center
number is stored on your SIM card and is dependent on your network operator. Contact your network operator for the correct SMS service center number." https://www.sony.co.uk/electronics/support/articles/SX055201

Anyway, further to my reply above, I put the sim in the Huawei and tried
to send a text. It failed again, and I got a text from Vodafone
(automatic reply?) with something relating to using a phone with updated software or it needing a new APN, and reference to a Vodafone webpage.
The webpage was of no use.

I played around a bit more and found the Huawei behaved exactly the same
as the Samsung. It could receive texts, and make and receive phone calls only - it could not send a text. I assume the sim is faulty.

An SMSC problem would affect any phone the SIM card is used in.

(unless it's a smartphone doing RCS, which is completely different transport)

Theo
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

Theo <theom+news@chiark.greenend.org.uk> wrote:

Jeff Layman <Jeff@invalid.invalid> wrote:

I hadn't heard of the SMSC number, but my first thought was why can the phone receive texts? If there was a problem with the SMSC, wouldn't it neither send nor receive texts?

"If you canrCOt send, but only receive, text messages, you might need to set the SMS service center number (SMSC) manually. The SMS service center
number is stored on your SIM card and is dependent on your network operator. Contact your network operator for the correct SMS service center number." https://www.sony.co.uk/electronics/support/articles/SX055201

I can confirm the procedure described there (dialling *#*#4636#*#* and
looking for the SMSC setting at the bottom) works on a modern non-Sony
Android too.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

On 23/07/2025 14:26, Theo wrote:

Theo <theom+news@chiark.greenend.org.uk> wrote:

Jeff Layman <Jeff@invalid.invalid> wrote:

I hadn't heard of the SMSC number, but my first thought was why can the
phone receive texts? If there was a problem with the SMSC, wouldn't it
neither send nor receive texts?

"If you canrCOt send, but only receive, text messages, you might need to set >> the SMS service center number (SMSC) manually. The SMS service center
number is stored on your SIM card and is dependent on your network operator. >> Contact your network operator for the correct SMS service center number."
https://www.sony.co.uk/electronics/support/articles/SX055201

I can confirm the procedure described there (dialling *#*#4636#*#* and looking for the SMSC setting at the bottom) works on a modern non-Sony Android too.

I tried *#*#4636#*#* and all I got was "wrong number".

And internet search on:
samsung smsc number vodafone -android

was of no help. Omitting the -android led mainly to Galaxy-related
issues. For example, this link suggests I'm not the only one to have
issues with SMSC: <https://eu.community.samsung.com/t5/other-galaxy-s-series/how-to-change-message-centre-number/td-p/3361569>

I'm wondering if, for my Samsung, this was something to do with the 3G
switch off.
--
Jeff
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

Jeff Layman <Jeff@invalid.invalid> wrote:

I tried *#*#4636#*#* and all I got was "wrong number".

That's the Android procedure, but it may get it working in the Huawei. The
SMSC is saved as a (hidden) contact on the SIM card so if you then move the
SIM to the Samsung it may work. Else look around the Samsung settings for
SMSC or Message Centre and set your network's SMSC there.

I'm wondering if, for my Samsung, this was something to do with the 3G switch off.

Could be SIM provisioning went wrong somehiw?

Theo

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.mobile

On 23/07/2025 20:26, Theo wrote:

Jeff Layman <Jeff@invalid.invalid> wrote:

I tried *#*#4636#*#* and all I got was "wrong number".

That's the Android procedure, but it may get it working in the Huawei. The SMSC is saved as a (hidden) contact on the SIM card so if you then move the SIM to the Samsung it may work. Else look around the Samsung settings for SMSC or Message Centre and set your network's SMSC there.

The phone won't call *#*#4636#*#* (NB it's Android 5.1). All the
characters can be entered, but as soon as the final * is entered the
dialling number pad disappears. If I go into Call settings and then
Additional settings, it displays:

Call settings error
Network or SIM card error.

Unfortunately, the Huawei can now no longer make or receive calls! I
replaced the sim in the Samsung, and that is working as it did before
trying *#*#4636#*#*.

Here endeth the lesson. Enough time wasted all round. :-)

I'm wondering if, for my Samsung, this was something to do with the 3G
switch off.

Could be SIM provisioning went wrong somehiw?

Who knows? Thanks for all the suggestions.
--
Jeff
--- Synchronet 3.21a-Linux NewsLink 1.2