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

Groups > comp.mobile.android > #32068 > unrolled thread

Very odd SMS problem, maybe someone can help.

Back to article view | Back to comp.mobile.android

Contents

  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

#32068 — Very odd SMS problem, maybe someone can help.

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.

[toc] | [next] | [standalone]

#32069

In article <nmirle$37v$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?

what happens if she sends by using an sms gateway or via computer
(i.e., *not* originating from her phone)?

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.

[toc] | [prev] | [next] | [standalone]

#32072

On 7/18/2016 11:24 AM, nospam wrote:
> In article <nmirle$37v$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.

>
> 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.
>
> 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.  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.

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.

[toc] | [prev] | [next] | [standalone]

#32073

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.

[toc] | [prev] | [next] | [standalone]

#32084

On 7/18/2016 12:04 PM, nospam wrote:
> 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?
Both AT&T, we have a shared plan.

>
> what happens if you swap sims? does the problem follow the sim or the
> phone?
>
> do you have a spare third phone to try?

I have my old LG Optimus G Pro laying around somewhere.  Good idea to 
try that. I can also try swapping the SIMs between our two phones.

>
>>> 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.

"Connected" is a better term I should have used.  I can pair a number of 
phones, only one at-a-time can be connected.

>
>> 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.

Can't hurt to try that.

>   
>   
>> 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.

[toc] | [prev] | [next] | [standalone]

#32092

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

> >>> 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.
> 
> "Connected" is a better term I should have used.  I can pair a number of 
> phones, only one at-a-time can be connected.

pairing is the correct term.

many bluetooth devices are multipoint and support pairings with more
than one phone.

when a call comes in (or text), a connection is established with the
correct phone.

it can even switch on the fly. you could be listening to a podcast from
one device (phone, tablet, ipod) and if a call comes in on a second
phone, it'll switch automatically.

[toc] | [prev] | [next] | [standalone]

#32105

On 7/18/2016 12:50 PM, nospam wrote:
> In article <nmivtl$j0f$2@dont-email.me>, PAS <abc@doremi.net> wrote:
>
>>>>> 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.
>> "Connected" is a better term I should have used.  I can pair a number of
>> phones, only one at-a-time can be connected.
> pairing is the correct term.
>
> many bluetooth devices are multipoint and support pairings with more
> than one phone.
>
> when a call comes in (or text), a connection is established with the
> correct phone.
>
> it can even switch on the fly. you could be listening to a podcast from
> one device (phone, tablet, ipod) and if a call comes in on a second
> phone, it'll switch automatically.

Perhaps my car's head units support this, haven't tried.  Let's suppose 
it does and present a scenario:  my wife and I are in the car together 
with bluetooth enabled on our phones.  Her phone is paired.  I receive a 
call on my phone.  If the system automatically then attempts to pair my 
phone, the time it takes to pair it takes a few seconds, at least.  By 
the time the pairing is complete, the call could have gone to voice mail.

[toc] | [prev] | [next] | [standalone]

#32113

In article <nmj70s$cvq$3@dont-email.me>, PAS <abc@doremi.net> wrote:

> >>>>> 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.
> >> "Connected" is a better term I should have used.  I can pair a number of
> >> phones, only one at-a-time can be connected.
> > pairing is the correct term.
> >
> > many bluetooth devices are multipoint and support pairings with more
> > than one phone.
> >
> > when a call comes in (or text), a connection is established with the
> > correct phone.
> >
> > it can even switch on the fly. you could be listening to a podcast from
> > one device (phone, tablet, ipod) and if a call comes in on a second
> > phone, it'll switch automatically.
> 
> Perhaps my car's head units support this, haven't tried.  Let's suppose 
> it does and present a scenario:  my wife and I are in the car together 
> with bluetooth enabled on our phones.  Her phone is paired.  I receive a 
> call on my phone.  If the system automatically then attempts to pair my 
> phone, the time it takes to pair it takes a few seconds, at least.  By 
> the time the pairing is complete, the call could have gone to voice mail.

pairing adds a device to its internal list, and maybe it limits it to
one phone at any given moment.

i have a bluetooth headset that can pair with up to 8 devices total,
but there can only be two active at any time. whichever phone gets a
call rings through to the headset, without delay.

[toc] | [prev] | [next] | [standalone]

#32116

On 7/18/2016 2:50 PM, nospam wrote:
> In article <nmj70s$cvq$3@dont-email.me>, PAS <abc@doremi.net> wrote:
>
>>>>>>> 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.
>>>> "Connected" is a better term I should have used.  I can pair a number of
>>>> phones, only one at-a-time can be connected.
>>> pairing is the correct term.
>>>
>>> many bluetooth devices are multipoint and support pairings with more
>>> than one phone.
>>>
>>> when a call comes in (or text), a connection is established with the
>>> correct phone.
>>>
>>> it can even switch on the fly. you could be listening to a podcast from
>>> one device (phone, tablet, ipod) and if a call comes in on a second
>>> phone, it'll switch automatically.
>> Perhaps my car's head units support this, haven't tried.  Let's suppose
>> it does and present a scenario:  my wife and I are in the car together
>> with bluetooth enabled on our phones.  Her phone is paired.  I receive a
>> call on my phone.  If the system automatically then attempts to pair my
>> phone, the time it takes to pair it takes a few seconds, at least.  By
>> the time the pairing is complete, the call could have gone to voice mail.
> pairing adds a device to its internal list, and maybe it limits it to
> one phone at any given moment.
>
> i have a bluetooth headset that can pair with up to 8 devices total,
> but there can only be two active at any time. whichever phone gets a
> call rings through to the headset, without delay.

Now that I think about it, neither of the head units in our cars allow 
for more than one active phone.  Both also establish a hierarchy whereby 
if two phones have bluetooth enabled, the first one on the list gets 
paired.  The order of the list is determined by the order each phone was 
first paired/registered.

[toc] | [prev] | [next] | [standalone]

#32277

On Mon, 18 Jul 2016 11:12:47 -0400, 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.

So I don't think this is because of the phone.  It's because of the
car.   Some high-end cars and specific lower priced models have a
Family Comm Package that prevents a wife from texting her husband in
the car.  I'll see if I can find their commercials online, where the
slogan was something like "A man needs time alone, without the hassles
of family". 

What make and model car do you have? 

>  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.

[toc] | [prev] | [next] | [standalone]

#32298

On 07/19/2016 06:04 PM, Micky wrote:

> So I don't think this is because of the phone.  It's because of the
> car.   Some high-end cars and specific lower priced models have a
> Family Comm Package that prevents a wife from texting her husband in
> the car.  I'll see if I can find their commercials online, where the
> slogan was something like "A man needs time alone, without the hassles
> of family".

Sexist pig!

Back in the dark ages one of the good things about being in your car was 
that nobody could get at you then.  You were free.

-- 
Cheers, Bev
*************************************************
Never argue with a woman holding a torque wrench.

[toc] | [prev] | [next] | [standalone]

#32301

In article <nmmna5$r6v$1@dont-email.me>, The Real Bev
<bashley101@gmail.com> wrote:

> Back in the dark ages one of the good things about being in your car was 
> that nobody could get at you then.  You were free.

that hasn't changed.

[toc] | [prev] | [next] | [standalone]

#32339

On Tue, 19 Jul 2016 19:23:01 -0700, The Real Bev
<bashley101@gmail.com> wrote:

>On 07/19/2016 06:04 PM, Micky wrote:
>
>> So I don't think this is because of the phone.  It's because of the
>> car.   Some high-end cars and specific lower priced models have a
>> Family Comm Package that prevents a wife from texting her husband in
>> the car.  I'll see if I can find their commercials online, where the
>> slogan was something like "A man needs time alone, without the hassles
>> of family".
>
>Sexist pig!

At least someone understands me. 

>Back in the dark ages one of the good things about being in your car was 
>that nobody could get at you then.  You were free.

Yes.  Women too. 

[toc] | [prev] | [next] | [standalone]

#32367

On 7/19/2016 9:04 PM, Micky wrote:
> On Mon, 18 Jul 2016 11:12:47 -0400, 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.
> So I don't think this is because of the phone.  It's because of the
> car.   Some high-end cars and specific lower priced models have a
> Family Comm Package that prevents a wife from texting her husband in
> the car.  I'll see if I can find their commercials online, where the
> slogan was something like "A man needs time alone, without the hassles
> of family".
>
> What make and model car do you have?

It's not an issue with any type of Comm Package.  I used to get the SMS 
messages in the car from my wife.  Then the problem arose not too long 
ago after an update to Android 6 where her phone started to truncate the 
area code of my number and I couldn't receive a text at all.  It only 
happened with my number, no one else's.  That got resolved somehow and 
now the problem is that I can't get the messages in the car via 
bluetooth from only her, I get them from everyone else.  We have a third 
phone on the account, my younger son's and I get his messages properly.

We have two Subarus, a 2014 Forester with the factory NAV system and a 
2015 Outback with the factory NAV system.  Each system is completely is 
completely different from the other.  The Forester uses an older 
system.  The 2015 Outback was the first Subaru to use a completely new 
system.  I believe it may be a Toyota designed system since Toyota owns 
a percentage of Subaru.

On a different note if anyone is interested, the Forester system vexed 
me in some ways (it vexed many other owners who had the same problem).  
It would restart at times and also reboot at times.  A restart was a 
quick shutdown and then an immediate restart of the system right back 
where it left off, it was only a few seconds.  A reboot was a complete 
shutdown and reboot of the system.  All settings would go back to 
default with the exception of saved radio presets, everything else would 
have to be reset.  I got to a point where I could reproduce the 
rebooting under very specific conditions:  play an MP3, drive the car 
for about three miles (preferably without stopping at a traffic light as 
a continuous drive was better to reproduce this), then wait for the 
system to reboot.  Each time I brought it to the dealership, they 
couldn't reproduce the problem.  At one particular time, I had my wife 
accompany me to the dealership and I reproduced the rebooting while she 
recorded it and gave them the video.  Still, the dealership needed to 
see it happen on the car and they couldn't reproduce it even though I 
told them just how I could do it. I met the service manager at the 
dealership, took him for a drive, and reproduced the problem.  They 
replaced the unit but since it's a design defect, it still would 
happen.  However, one positive thing about the replacement is that when 
our LG phones were updated to Android 5, receiving text messaging no 
longer worked properly.  If you got a new message, the system would read 
back every text message you had on your phone. The replacement system 
did not do that, obviously it has a newer firmware version.  But it 
still wouldn't display caller ID of any contact correctly, neither the 
older unit nor the replacement.  Every contact that called was an 
"unknown number" even though they were in the contacts.  Well, it seems 
that is a device-specific problem because now that I replaced our LG 
phones with two BLU phones, caller ID now works properly.

>
>>   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.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.mobile.android

csiph-web