Can't message the wife, skinny

Forums › Spark New Zealand (including Skinny and BigPipe) › Can't message the wife, skinny - skinny

1 | 2 | 3 | 4

120 posts

Master Geek

#2617170 7-Dec-2020 01:14

I thought I was the only one. I to was having problems sending a txt message to one person only. Skinny - 2degrees
What worked for me also was to go into contacts edit change nothing then save.

Thanks to this thread :)

freitasm

BDFL - Memuneh
79250 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#2617190 7-Dec-2020 07:32

Any or both of you using Messages Chat - even if the other party activated it and forgot to tell you during troubleshooting?

ageorge

626 posts

Ultimate Geek

#2617207 7-Dec-2020 08:34

freitasm:

Any or both of you using Messages Chat - even if the other party activated it and forgot to tell you during troubleshooting?

Nope, never used Chat, although checked its options to make sure it was not part of the issue.

I would seem that Google Messages may be the culprit in some way. Its sending with errant status flags or similar, otherwise Skinny would not reply with an error message.

jamesrt

1609 posts

Uber Geek

ID Verified

Trusted

Lifetime subscriber

#2617212 7-Dec-2020 08:54

I also recently had an issue with Google Messages App (NOT using chat features); where I needed to reset the app completely - (clear data & cache) before I could send texts - two numbers affected, both which I message frequently via SMS.

Whilst the Google app was playing up "Chomp" (my old SMS software I used to use on another device) worked perfectly.

Starting to sound like Google Messages has issues... Which doesn't surprise me; Google do break things frequently and sometimes they never get fixed properly.

(I *still* can't use the voice-enabled features on my WearOS watch to dictate an SMS message UNLESS I have my PHONE set to US English. Go figure. Whats worse is if you factory-reset the watch, it all works perfectly up until it downloads the Google updates... I know, that's off-topic)

ageorge

626 posts

Ultimate Geek

#2617221 7-Dec-2020 09:08

jamesrt:

I also recently had an issue with Google Messages App (NOT using chat features); where I needed to reset the app completely - (clear data & cache) before I could send texts - two numbers affected, both which I message frequently via SMS

Hmm, clearing cache is always my first port of call, though I did not clear data.

weetbix43

120 posts

Master Geek

#2617776 7-Dec-2020 20:22

I am just using the default to send txt messages. Open the app and click start chat.

linw

2849 posts

Uber Geek

#2618029 8-Dec-2020 11:25

Funny, but I had that prob a few days ago, skinny-skinny. What fixed mine was re-booting my phone.

Equinox IT

Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.

freitasm

BDFL - Memuneh
79250 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#2620403 12-Dec-2020 09:46

Could you folks go to Settings | Apps find Carrier Services and see what version it's installed?

Apparently v50 has a problem with some operators and currently Google is rolling back to v48.

linw

2849 posts

Uber Geek

#2620421 12-Dec-2020 10:26

Mine is 48.

Villager

22 posts

Geek

#2625620 22-Dec-2020 19:44

I found this thread... same problem. Error 38.

Was texting an associate - no problem two texts. He is on Vodafone. I'm on Skinny (Pixel 2 XL - Android 11).
3rd text - "Not sent - Tap to try again." Ditto 4th text
Tried to call him - says the number is not working
He rang me a minute later. No problem inbound.
Texting to everyone else as normal.
Two days later, I responded to his text. Same "Not sent - Tap to try again."
Pulled out my backup Moto G4 phone, also on Skinny. No problem texting or calling him.
Sent a text to my ancient Vodafone Nokia 6822 to make sure it was not a problem texting Vodafone. Worked fine.
Called Skinny. They told me to buy a new sim card
Bought a new sim card and ported my number over to it. No difference.
Found this thread. Added Chomp to my phone and made it the default
Message went through fine. He replied.
Went back to Google Messages. It showed the successful Chomp text.
Tried to send a new text. Same error.

It appears the problem is Google Messages. Odd that it is only one contact.

Awaiting someone actually determining what's wrong.

freitasm

BDFL - Memuneh
79250 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#2625623 22-Dec-2020 19:51

Villager:

It appears the problem is Google Messages. Odd that it is only one contact.

Awaiting someone actually determining what's wrong.

Can't be just Google Messages as you tried calling and the number did not connect.

Villager

22 posts

Geek

#2625632 22-Dec-2020 20:22

freitasm:

Villager:

It appears the problem is Google Messages. Odd that it is only one contact.

Awaiting someone actually determining what's wrong.

Can't be just Google Messages as you tried calling and the number did not connect.

True, and it may be that the update to Google 11 has some bugs. I've also noted non-responsiveness on Google maps, and it took forever to reboot when I was trying to catch an Uber causing me to miss my appointment.

The cynical part of me wonders if there are intentional aggravations built into the update so I will buy a new phone now that Google says it's at the end of support for the Pixel 2 XL. But of course, big-tech would never do such a thing as that, so we must work out why messaging continues to fail, and other apps get sticky. Maybe it's time to start carrying the Nokia 6822 again. It's battery lasts six days and it has a fold-out keyboard for texting.

weetbix43

120 posts

Master Geek

#2625654 22-Dec-2020 21:50

freitasm:
Could you folks go to Settings | Apps find Carrier Services and see what version it's installed?

Apparently v50 has a problem with some operators and currently Google is rolling back to v48.

ver 48

BlindBakerNZ

3 posts

Wannabe Geek

#2649535 8-Feb-2021 15:59

I have been struggling with this for a while and I have narrowed it down quite a bit.

This only happens to me after I try to send a text using the google assistant, after that that contact is blocked in the messages app. The best way I have found to get it working again is to delete the conversation, then delete all cache and data from the messages app.

It appears that something funny happens when google assistant sends the message, and only on the Spark networks. I have tried inserting a 2 degrees SIM in my Pixel 2XL and it works fine. I can also put my Skinny or Slingshot SIM cards in a Huawei phone and it gets the same error.

I have logged an issue with Google, and I think everyone needs to do this for them to fix it.

CapBBeard

211 posts

Master Geek

#2814096 16-Nov-2021 22:10

Chalk up another one with this exact issue.

My wife (Skinny) is unable to SMS her father (Spark). There seems to be finger pointing back and forth between the two carriers but no one is able to help us out. Then I found this thread - and can describe identical behaviour.

Google Messages app, just the one contact affected, no obvious cause or solution. "Error 38". Did anyone ever get to the bottom of this?

Cheers!

1 | 2 | 3 | 4