Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.mobile.android > #32073

Re: Very odd SMS problem, maybe someone can help.

Show all headers | View raw

In article <nmiu88$ckm$2@dont-email.me>, PAS <abc@doremi.net> wrote:

> >> I've got a strange issue with my wife's phone.  AT&T has been little
> >> help and I think it's because it's such an odd problem.  I cannot
> >> receive SMS messages from my wife's phone via bluetooth in either of our
> >> two cars.  I get them on my phone, they just don't come over the car
> >> stereo systems.  This only happens with SMS messages from her, I get SMS
> >> messages from everyone else over the car stereo systems.  This isn't
> >> device-specific.  It started when we both had LG G3 phones and after
> >> they were updated to Android 6.  I recently got an LG G5 and the problem
> >> was still there.  I returned the G5 because it was defective and bought
> >> a BLU Pure XL and also got one for my wife so she's no longer using her
> >> G3 and the problem still exists.  The BLU phones have Android 5.1.
> >>
> >> After the LG G3 was upgraded to Android 6 (not immediately after but a
> >> short time after), my wife couldn't send me any SMS messages.  They
> >> weren't getting through to my phone.  I noticed that her phone was
> >> truncating the area code of my phone number. You can't send an SMS
> >> without an area code.  My contact was properly entered in her contact
> >> list with the area code.  When she typed the message, my area code was
> >> there and then when she'd press send, the area code would get
> >> truncated.  AT&T suggested to delete my contacts, clear the cache, and
> >> re-enter my contact on her phone.  After doing this several times, it
> >> cleared up the problem of truncating my area code and she could send me
> >> SMS messages again.  But the problem of not receiving the SMS message
> >> via bluetooth over the car stereo systems still exists.  If it was
> >> happening no matter who sends the messages then it might be easier to
> >> resolve but it's only messages from her.
> > what about the other direction, you sending to her?
> 
> Me sending her works fine, this makes it all the more baffling.  I 
> checked the settings in both of our SMS apps and they are the same.

both at&t?

what happens if you swap sims? does the problem follow the sim or the
phone?

do you have a spare third phone to try?

> > what happens if she sends by using an sms gateway or via computer
> > (i.e., *not* originating from her phone)?
> 
> Haven't tried that, that's a good thought.  I'll have her try this this 
> evening.

ok

> > are both phones paired with the same vehicle? if so, un-pair one and
> > test, or better yet, unpair both phones and test as you re-pair each
> > one. if possible, reset the vehicle's bluetooth completely (unpairing
> > *everything*) and then re-pair.
> 
> The systems only allow one phone to be paired at any time. 

eh? why? most families have more than one driver per vehicle.

> I tested it 
> yesterday while my phone was paired and her phone was not.  I thought 
> about unpairing the phones but the two phones are brand-new and were 
> paired for the first time in her car yesterday which is where I tested 
> it.    Good questions, thanks.

try unpairing anyway. 
 
> On a side note, my car (2014 Subaru Forester) has the much-maligned 
> Harman/Kardon Navigation head unit.  As long as I've had the car, I had 
> my LG G3 and it was running Android 5 and then 6.  The caller ID never 
> worked on that unit for anyone in my contacts, every caller was 
> "unknown".  My thought was that it was attributed to using Google 
> contacts which automatically adds "+1" to every phone number and that 
> the software in the head unit didn't read it properly.  It was 
> frustrating.  With the BLU phones, caller ID works fine.  That problem 
> appears to be device-specific.

prepending +1 for usa numbers is correct, as that's the country code.

not parsing that properly means the system isn't likely to work for any
international calls.

Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Very odd SMS problem, maybe someone can help. PAS <abc@doremi.net> - 2016-07-18 11:12 -0400
  Re: Very odd SMS problem, maybe someone can help. nospam <nospam@nospam.invalid> - 2016-07-18 11:24 -0400
    Re: Very odd SMS problem, maybe someone can help. PAS <abc@doremi.net> - 2016-07-18 11:56 -0400
      Re: Very odd SMS problem, maybe someone can help. nospam <nospam@nospam.invalid> - 2016-07-18 12:04 -0400
        Re: Very odd SMS problem, maybe someone can help. PAS <abc@doremi.net> - 2016-07-18 12:25 -0400
          Re: Very odd SMS problem, maybe someone can help. nospam <nospam@nospam.invalid> - 2016-07-18 12:50 -0400
            Re: Very odd SMS problem, maybe someone can help. PAS <abc@doremi.net> - 2016-07-18 14:26 -0400
              Re: Very odd SMS problem, maybe someone can help. nospam <nospam@nospam.invalid> - 2016-07-18 14:50 -0400
                Re: Very odd SMS problem, maybe someone can help. PAS <abc@doremi.net> - 2016-07-18 15:17 -0400
  Re: Very odd SMS problem, maybe someone can help. Micky <NONONObobbyburns1111@gmail.com> - 2016-07-19 21:04 -0400
    Re: Very odd SMS problem, maybe someone can help. The Real Bev <bashley101@gmail.com> - 2016-07-19 19:23 -0700
      Re: Very odd SMS problem, maybe someone can help. nospam <nospam@nospam.invalid> - 2016-07-19 22:54 -0400
      Re: Very odd SMS problem, maybe someone can help. Micky <NONONObobbyburns1111@gmail.com> - 2016-07-20 04:18 -0400
    Re: Very odd SMS problem, maybe someone can help. PAS <abc@doremi.net> - 2016-07-20 10:07 -0400

csiph-web