RE: for Joshua
I've never had a situation where apple have forced me to take on an update to my devices. -Original Message- From: viphone@googlegroups.com On Behalf Of chalt...@gmail.com Sent: Monday, 31 August 2020 1:50 PM To: viphone@googlegroups.com Subject: RE: for Joshua Apple already aggressively pushes out updates to their devices, for example, within a few days of a release, you won't be able to roll back to a previous release. Plus they drop pushing out security updates once a newer release has been deployed. With the adoption rate Apple has with new releases, I doubt it would be a serious PR issue for them to stop providing customer support for a release that's been superseded by a newer release that's still getting security updates. Apple wouldn't be the first company to ask you to update to a newer version of software before providing you support. Sometimes this is legitimate, since newer versions of the software will contain fixes for issues being reported to customer support. . You may be able to stay on IOS 12.4.1, but there's no guarantee that Apple will continue to provide customer support for an unsupported version of IOS. Don't get me wrong, I don't have a problem with you staying on IOS 12.4.1 as long as you want. My only reason for posting is to let others know that there's no obligation or guarantee from Apple to support 12.4.1 forever. Plus, anyone who stays on IOS 12.4.1 will be missing out on security patches and may not get support from app developers on 12.4.1. I'm totally on board with people having the right to choose, as long as they're given accurate information to make that choice. -- Christopher (AKA CJ) Chaltain at Gmail > -Original Message- > From: viphone@googlegroups.com On Behalf Of > Robin > Sent: Sunday, August 30, 2020 4:04 PM > To: viphone@googlegroups.com > Subject: RE: for Joshua > > Oh, but "They" Because I have AppleCare+ on it, & it would be a Bad > PR Move not to Support it. Pressuring a Consumer to Update a > SoftwareVersion, which "They" (Apple) deemed ReadyFor PublicRelease . > It's MyRight, as a Consumer Not to Update MyDevice'sSoftware & there > isn't AnyWhere in AppleCare+ that Sayz that I must, & I Called & > CheckedWith Apple's AppleAccessibility TelephoneSupport, & "They" > indicated that I wouldn't Be Denied & that's that. > > At 08:33 AM 8/30/2020, you wrote: > >I'm not sure why you think Apple can't deny you telephone support for > >an older unsupported version of IOS. You may be getting telephone > >support for now, but I doubt it'll last forever. > >I'm pretty sure Apple isn't releasing security updates for 12.4.1 any > >more either. Plus there's nothing that says app developers have to > >continue to support 12.4.1. > > > >-- > >Christopher (AKA CJ) > >Chaltain at Gmail > > > > > -Original Message- > > > From: viphone@googlegroups.com On > Behalf > > > Of Robin > > > Sent: Saturday, August 29, 2020 8:59 PM > > > To: viphone@googlegroups.com > > > Subject: Re: for Joshua > > > > > > Okay, Ms. Shirley > > >After I received Your MessagePosting, which AppearsBelow > > > this MessagePosting of Mine, I decided to Call Apple's > > > AppleAccessibility TelephoneSupport @ 877-204-3930, To InQuire > > > about "what" you said, & I was informed that I wouldn't Be Denied > > > TelephoneSupport from Apple's AppleAccessibility because I > > > refused to update My VZW XS MAX from > > > iOS12.4.1 to WhatEver is the Latest iOS13 iteration. > > > > > > (I Presume) > > > it's because I didn't Update Past iOS12, > > as if I did "they" could say that the > > > BugFixes were Resolved in a Future iOS > > update of iOS13, but since I refused to > > > UpdatePast iOS12.4.1, I can't Be Denied TelephoneSupport from > > > AppleAccessibility on My VZW XS MAX At 06:30 PM 8/29/2020, you wrote: > > > >I just hope the device you don't have it on, you won't need help > > > >from Apple Accessibility because they told me they require you to > > > >have whatever device you're requesting help with, to be updated > > > >to the latest version or they won't help you so every since they > > > >told me that, I make sure my devices are all updated. > > > > > > > >Sent from my iPhone > > > > > > > > > On Aug 29, 2020, at 4:52 PM, R
Re: IOS updates [was "RE: for Joshua"]
That's "why" I won't Update My XS MAX & its Not Too Old of an iOSDevice for Apple to DenySupport Don't Hate? Congratulate! At 07:36 PM 8/30/2020, you wrote: The reason Apple pushed out IOS 12.4.7 on May 20, 2020, is to support those devices that Apple still supports but which don't support IOS 13. The following page says that IOS 12.4.7 is available for iPhone 5s, iPhone 6, iPhone 6 Plus, iPad Air, iPad mini 2, iPad mini 3, and iPod touch 6th generation. The iPhone XS is not listed. The only version of IOS listed for the XS is IOS 13. https://support.apple.com/en-us/HT201222 -- Christopher (AKA CJ) Chaltain at Gmail > -Original Message- > From: viphone@googlegroups.com On Behalf > Of Robin > Sent: Sunday, August 30, 2020 9:03 PM > To: viphone@googlegroups.com > Subject: RE: for Joshua > > if "what" ya say IS True, then "why" Did Apple PushOut iOS SecurityUpdates to > Older iOSVersions Like iOS9 & iOS10 as well as iOS12, When their > (current) iteration of iOS IS iOS13? > Because of the PR i.e., SecurityBreaches to those Versions of iOS Don'tKnow > "why" You AppleFanBoyz Push Others to Update Their iOSDevices, & Hate on > Them when Doing so, Breaks "accessibility" For Them & They Criticize Apple for > its "Bugs" & Flaws" > i.e., the "Bugs" & "Flaws" of iOS8 & > MoreRecently iOS13, as Apple quickly Relased & PushedOut iOSUpdates within > 72Hours of the Relase of a NEW iPhone > > At 06:49 PM 8/30/2020, you wrote: > >Apple already aggressively pushes out updates to their devices, for > >example, within a few days of a release, you won't be able to roll back > >to a previous release. Plus they drop pushing out security updates once > >a newer release has been deployed. With the adoption rate Apple has > >with new releases, I doubt it would be a serious PR issue for them to > >stop providing customer support for a release that's been superseded by > >a newer release that's still getting security updates. Apple wouldn't > >be the first company to ask you to update to a newer version of > >software before providing you support. Sometimes this is legitimate, > >since newer versions of the software will contain fixes for issues > >being reported to customer support. . You may be able to stay on IOS > >12.4.1, but there's no guarantee that Apple will continue to provide > >customer support for an unsupported version of IOS. > > > >Don't get me wrong, I don't have a problem with you staying on IOS > >12.4.1 as long as you want. > >My only reason for posting is to let others know that there's no > >obligation or guarantee from Apple to support 12.4.1 forever. Plus, > >anyone who stays on IOS 12.4.1 will be missing out on security patches > >and may not get support from app developers on 12.4.1. I'm totally on > >board with people having the right to choose, as long as they're given > >accurate information to make that choice. > > > >-- > >Christopher (AKA CJ) > >Chaltain at Gmail > > > > > -Original Message- > > > From: viphone@googlegroups.com On > Behalf > > > Of Robin > > > Sent: Sunday, August 30, 2020 4:04 PM > > > To: viphone@googlegroups.com > > > Subject: RE: for Joshua > > > > > > Oh, but "They" Because I have AppleCare+ on > > it, & it would be a Bad PR Move > > > not to Support it. Pressuring a Consumer > > to Update a SoftwareVersion, which > > > "They" (Apple) deemed ReadyFor PublicRelease . It's MyRight, as a > > > Consumer Not to Update MyDevice'sSoftware & there isn't AnyWhere in > > > AppleCare+ that Sayz that I must, & I Called & CheckedWith Apple's > > > AppleAccessibility TelephoneSupport, & "They" > > > indicated that I wouldn't Be Denied & that's that. > > > > > > At 08:33 AM 8/30/2020, you wrote: > > > >I'm not sure why you think Apple can't deny you telephone support > > > >for an older unsupported version of IOS. You may be getting > > > >telephone support for now, but I doubt it'll last forever. > > > >I'm pretty sure Apple isn't releasing security updates for 12.4.1 > > > >any more either. Plus there's nothing that says app developers have > > > >to continue to support 12.4.1. > > > > > > > >-- > > > >Christopher (AKA CJ) > > > >Ch
IOS updates [was "RE: for Joshua"]
The reason Apple pushed out IOS 12.4.7 on May 20, 2020, is to support those devices that Apple still supports but which don't support IOS 13. The following page says that IOS 12.4.7 is available for iPhone 5s, iPhone 6, iPhone 6 Plus, iPad Air, iPad mini 2, iPad mini 3, and iPod touch 6th generation. The iPhone XS is not listed. The only version of IOS listed for the XS is IOS 13. https://support.apple.com/en-us/HT201222 -- Christopher (AKA CJ) Chaltain at Gmail > -Original Message- > From: viphone@googlegroups.com On Behalf > Of Robin > Sent: Sunday, August 30, 2020 9:03 PM > To: viphone@googlegroups.com > Subject: RE: for Joshua > > if "what" ya say IS True, then "why" Did Apple PushOut iOS SecurityUpdates > to > Older iOSVersions Like iOS9 & iOS10 as well as iOS12, When their > (current) iteration of iOS IS iOS13? > Because of the PR i.e., SecurityBreaches to those Versions of iOS Don'tKnow > "why" You AppleFanBoyz Push Others to Update Their iOSDevices, & Hate on > Them when Doing so, Breaks "accessibility" For Them & They Criticize Apple for > its "Bugs" & Flaws" > i.e., the "Bugs" & "Flaws" of iOS8 & > MoreRecently iOS13, as Apple quickly Relased & PushedOut iOSUpdates within > 72Hours of the Relase of a NEW iPhone > > At 06:49 PM 8/30/2020, you wrote: > >Apple already aggressively pushes out updates to their devices, for > >example, within a few days of a release, you won't be able to roll back > >to a previous release. Plus they drop pushing out security updates once > >a newer release has been deployed. With the adoption rate Apple has > >with new releases, I doubt it would be a serious PR issue for them to > >stop providing customer support for a release that's been superseded by > >a newer release that's still getting security updates. Apple wouldn't > >be the first company to ask you to update to a newer version of > >software before providing you support. Sometimes this is legitimate, > >since newer versions of the software will contain fixes for issues > >being reported to customer support. . You may be able to stay on IOS > >12.4.1, but there's no guarantee that Apple will continue to provide > >customer support for an unsupported version of IOS. > > > >Don't get me wrong, I don't have a problem with you staying on IOS > >12.4.1 as long as you want. > >My only reason for posting is to let others know that there's no > >obligation or guarantee from Apple to support 12.4.1 forever. Plus, > >anyone who stays on IOS 12.4.1 will be missing out on security patches > >and may not get support from app developers on 12.4.1. I'm totally on > >board with people having the right to choose, as long as they're given > >accurate information to make that choice. > > > >-- > >Christopher (AKA CJ) > >Chaltain at Gmail > > > > > -Original Message- > > > From: viphone@googlegroups.com On > Behalf > > > Of Robin > > > Sent: Sunday, August 30, 2020 4:04 PM > > > To: viphone@googlegroups.com > > > Subject: RE: for Joshua > > > > > > Oh, but "They" Because I have AppleCare+ on > > it, & it would be a Bad PR Move > > > not to Support it. Pressuring a Consumer > > to Update a SoftwareVersion, which > > > "They" (Apple) deemed ReadyFor PublicRelease . It's MyRight, as a > > > Consumer Not to Update MyDevice'sSoftware & there isn't AnyWhere in > > > AppleCare+ that Sayz that I must, & I Called & CheckedWith Apple's > > > AppleAccessibility TelephoneSupport, & "They" > > > indicated that I wouldn't Be Denied & that's that. > > > > > > At 08:33 AM 8/30/2020, you wrote: > > > >I'm not sure why you think Apple can't deny you telephone support > > > >for an older unsupported version of IOS. You may be getting > > > >telephone support for now, but I doubt it'll last forever. > > > >I'm pretty sure Apple isn't releasing security updates for 12.4.1 > > > >any more either. Plus there's nothing that says app developers have > > > >to continue to support 12.4.1. > > > > > > > >-- > > > >Christopher (AKA CJ) > > > >Chaltain at Gmail > > > > > > > > > -Original Message- > > > > > From: viphone@googlegroups.com On > > > Behalf > > > > > Of Robin
Re: for Joshua
Great to Hear that! No HardFeelin's Here either. At 06:57 PM 8/30/2020, you wrote: No problem with anyone here. I always update within a few days after an update has come out for the reasons others have stated. Sent from my iPhone > On Aug 30, 2020, at 8:53 PM, chalt...@gmail.com wrote: > > Thanks Sherry. Yes, I was agreeing with Shirley and disagreeing with Robin. In fact, I assumed Shirley's response was directed at Robin's message, the same message I was responding to. > > -- > Christopher (AKA CJ) > Chaltain at Gmail > >> -Original Message- >> From: viphone@googlegroups.com On Behalf >> Of sherrywells1...@gmail.com >> Sent: Sunday, August 30, 2020 1:55 PM >> To: viphone@googlegroups.com >> Subject: RE: for Joshua >> >> Christopher wasn't saying he didn't believe you. He was saying he didn't know >> why you would think Apple could not refuse to help you unless you were on a >> more current version. Reread his post more carefully. >> >> Sherry Wells >> >> -Original Message- >> From: viphone@googlegroups.com On Behalf >> Of Shirley Baker >> Sent: Sunday, August 30, 2020 2:00 PM >> To: viphone@googlegroups.com >> Subject: Re: for Joshua >> >> I didn't think it up. This is what they told me and I can't help what your opinion >> might be but this particular person would not help me unless I updated my phone >> at that time. Whatever you believe is not my problem. I'm just telling you what >> that person said so I did what they told me to do and have ever since. >> >> Sent from my iPhone >> >>>> On Aug 30, 2020, at 10:33 AM, chalt...@gmail.com wrote: >>> >>> I'm not sure why you think Apple can't deny you telephone support for an older >> unsupported version of IOS. You may be getting telephone support for now, but >> I doubt it'll last forever. I'm pretty sure Apple isn't releasing security updates for >> 12.4.1 any more either. Plus there's nothing that says app developers have to >> continue to support 12.4.1. >>> >>> -- >>> Christopher (AKA CJ) >>> Chaltain at Gmail >>> >>>> -Original Message- >>>> From: viphone@googlegroups.com On >> Behalf >>>> Of Robin >>>> Sent: Saturday, August 29, 2020 8:59 PM >>>> To: viphone@googlegroups.com >>>> Subject: Re: for Joshua >>>> >>>> Okay, Ms. Shirley >>>> After I received Your MessagePosting, which AppearsBelow this >>>> MessagePosting of Mine, I decided to Call Apple's >>>> AppleAccessibility TelephoneSupport @ 877-204-3930, To InQuire about >>>> "what" you said, & I was informed that I wouldn't Be Denied >>>> TelephoneSupport from Apple's AppleAccessibility because I refused >>>> to update My VZW XS MAX from >>>> iOS12.4.1 to WhatEver is the Latest iOS13 iteration. >>>> >>>> (I Presume) >>>> it's because I didn't Update Past iOS12, as if I did "they" >>>> could say that the BugFixes were Resolved in a Future iOS update of >>>> iOS13, but since I refused to UpdatePast iOS12.4.1, I can't Be >>>> Denied TelephoneSupport from AppleAccessibility on My VZW XS MAX At >> 06:30 PM 8/29/2020, you wrote: >>>>> I just hope the device you don't have it on, you won't need help >>>>> from Apple Accessibility because they told me they require you to >>>>> have whatever device you're requesting help with, to be updated to >>>>> the latest version or they won't help you so every since they told >>>>> me that, I make sure my devices are all updated. >>>>> >>>>> Sent from my iPhone >>>>> >>>>>>> On Aug 29, 2020, at 4:52 PM, Robin wrote: >>>>>>> >>>>>>> You Ask? How will "I Know"? >>>>>>> If Ya ReadMyReplyMessagePosting to >>>>> ThisThread, I said, that I have Apple's iOS13 on My VZW 11PRO >>>>> PrimarilyBecause that is the iOS version that it was LaunchedWith, >>>>> but My VZW XS MAX wasn't, & Because of TheBugs >>>>> AssociatedWith iOS13, I Refuse to Update it >>>>> to iOS13, so it Remains on its Last Update, which is iOS12.4.1. >>>>>> MayBe just MayBe >>>>>> You're
RE: for Joshua
if Ya PaidAttention: I Don'tThink it was, as it wasn't MyMessagePosting that She was RespondingTo there. Not to Say, that She didn't Dispute this Matter with me because She did, & there were No Hard Feelings either way as Far as I know. At 06:53 PM 8/30/2020, you wrote: Thanks Sherry. Yes, I was agreeing with Shirley and disagreeing with Robin. In fact, I assumed Shirley's response was directed at Robin's message, the same message I was responding to. -- Christopher (AKA CJ) Chaltain at Gmail > -Original Message- > From: viphone@googlegroups.com On Behalf > Of sherrywells1...@gmail.com > Sent: Sunday, August 30, 2020 1:55 PM > To: viphone@googlegroups.com > Subject: RE: for Joshua > > Christopher wasn't saying he didn't believe you. He was saying he didn't know > why you would think Apple could not refuse to help you unless you were on a > more current version. Reread his post more carefully. > > Sherry Wells > > -Original Message- > From: viphone@googlegroups.com On Behalf > Of Shirley Baker > Sent: Sunday, August 30, 2020 2:00 PM > To: viphone@googlegroups.com > Subject: Re: for Joshua > > I didn't think it up. This is what they told me and I can't help what your opinion > might be but this particular person would not help me unless I updated my phone > at that time. Whatever you believe is not my problem. I'm just telling you what > that person said so I did what they told me to do and have ever since. > > Sent from my iPhone > > > On Aug 30, 2020, at 10:33 AM, chalt...@gmail.com wrote: > > > > I'm not sure why you think Apple can't deny you telephone support for an older > unsupported version of IOS. You may be getting telephone support for now, but > I doubt it'll last forever. I'm pretty sure Apple isn't releasing security updates for > 12.4.1 any more either. Plus there's nothing that says app developers have to > continue to support 12.4.1. > > > > -- > > Christopher (AKA CJ) > > Chaltain at Gmail > > > >> -Original Message- > >> From: viphone@googlegroups.com On > Behalf > >> Of Robin > >> Sent: Saturday, August 29, 2020 8:59 PM > >> To: viphone@googlegroups.com > >> Subject: Re: for Joshua > >> > >> Okay, Ms. Shirley > >> After I received Your MessagePosting, which AppearsBelow this > >> MessagePosting of Mine, I decided to Call Apple's > >> AppleAccessibility TelephoneSupport @ 877-204-3930, To InQuire about > >> "what" you said, & I was informed that I wouldn't Be Denied > >> TelephoneSupport from Apple's AppleAccessibility because I refused > >> to update My VZW XS MAX from > >> iOS12.4.1 to WhatEver is the Latest iOS13 iteration. > >> > >> (I Presume) > >> it's because I didn't Update Past iOS12, as if I did "they" > >> could say that the BugFixes were Resolved in a Future iOS update of > >> iOS13, but since I refused to UpdatePast iOS12.4.1, I can't Be > >> Denied TelephoneSupport from AppleAccessibility on My VZW XS MAX At > 06:30 PM 8/29/2020, you wrote: > >>> I just hope the device you don't have it on, you won't need help > >>> from Apple Accessibility because they told me they require you to > >>> have whatever device you're requesting help with, to be updated to > >>> the latest version or they won't help you so every since they told > >>> me that, I make sure my devices are all updated. > >>> > >>> Sent from my iPhone > >>> > >>>>> On Aug 29, 2020, at 4:52 PM, Robin wrote: > >>>>> > >>>>> You Ask? How will "I Know"? > >>>>> If Ya ReadMyReplyMessagePosting to > >>> ThisThread, I said, that I have Apple's iOS13 on My VZW 11PRO > >>> PrimarilyBecause that is the iOS version that it was LaunchedWith, > >>> but My VZW XS MAX wasn't, & Because of TheBugs > >>> AssociatedWith iOS13, I Refuse to Update it > >>> to iOS13, so it Remains on its Last Update, which is iOS12.4.1. > >>>> MayBe just MayBe > >>>> You're More TechSavy than I am. Yeah, > >>> that's MostLikely TheCase, as I'm not that TechSavy > >>>> > >>>> MyApologies, if this MessagePosting offends, as it isn't intended ToDoSo. > >>>> I'm just Stating-the-Facts, as "I See&qu
RE: for Joshua
if "what" ya say IS True, then "why" Did Apple PushOut iOS SecurityUpdates to Older iOSVersions Like iOS9 & iOS10 as well as iOS12, When their (current) iteration of iOS IS iOS13? Because of the PR i.e., SecurityBreaches to those Versions of iOS Don'tKnow "why" You AppleFanBoyz Push Others to Update Their iOSDevices, & Hate on Them when Doing so, Breaks "accessibility" For Them & They Criticize Apple for its "Bugs" & Flaws" i.e., the "Bugs" & "Flaws" of iOS8 & MoreRecently iOS13, as Apple quickly Relased & PushedOut iOSUpdates within 72Hours of the Relase of a NEW iPhone At 06:49 PM 8/30/2020, you wrote: Apple already aggressively pushes out updates to their devices, for example, within a few days of a release, you won't be able to roll back to a previous release. Plus they drop pushing out security updates once a newer release has been deployed. With the adoption rate Apple has with new releases, I doubt it would be a serious PR issue for them to stop providing customer support for a release that's been superseded by a newer release that's still getting security updates. Apple wouldn't be the first company to ask you to update to a newer version of software before providing you support. Sometimes this is legitimate, since newer versions of the software will contain fixes for issues being reported to customer support. . You may be able to stay on IOS 12.4.1, but there's no guarantee that Apple will continue to provide customer support for an unsupported version of IOS. Don't get me wrong, I don't have a problem with you staying on IOS 12.4.1 as long as you want. My only reason for posting is to let others know that there's no obligation or guarantee from Apple to support 12.4.1 forever. Plus, anyone who stays on IOS 12.4.1 will be missing out on security patches and may not get support from app developers on 12.4.1. I'm totally on board with people having the right to choose, as long as they're given accurate information to make that choice. -- Christopher (AKA CJ) Chaltain at Gmail > -----Original Message- > From: viphone@googlegroups.com On Behalf > Of Robin > Sent: Sunday, August 30, 2020 4:04 PM > To: viphone@googlegroups.com > Subject: RE: for Joshua > > Oh, but "They" Because I have AppleCare+ on it, & it would be a Bad PR Move > not to Support it. Pressuring a Consumer to Update a SoftwareVersion, which > "They" (Apple) deemed ReadyFor PublicRelease . It's MyRight, as a Consumer > Not to Update MyDevice'sSoftware & there isn't AnyWhere in AppleCare+ that > Sayz that I must, & I Called & CheckedWith Apple's AppleAccessibility > TelephoneSupport, & "They" > indicated that I wouldn't Be Denied & that's that. > > At 08:33 AM 8/30/2020, you wrote: > >I'm not sure why you think Apple can't deny you telephone support for > >an older unsupported version of IOS. You may be getting telephone > >support for now, but I doubt it'll last forever. > >I'm pretty sure Apple isn't releasing security updates for 12.4.1 any > >more either. Plus there's nothing that says app developers have to > >continue to support 12.4.1. > > > >-- > >Christopher (AKA CJ) > >Chaltain at Gmail > > > > > -Original Message- > > > From: viphone@googlegroups.com On > Behalf > > > Of Robin > > > Sent: Saturday, August 29, 2020 8:59 PM > > > To: viphone@googlegroups.com > > > Subject: Re: for Joshua > > > > > > Okay, Ms. Shirley > > >After I received Your MessagePosting, which AppearsBelow this > > > MessagePosting of Mine, I decided to Call Apple's > > > AppleAccessibility TelephoneSupport @ 877-204-3930, To InQuire about > > > "what" you said, & I was informed that I wouldn't Be Denied > > > TelephoneSupport from Apple's AppleAccessibility because I refused > > > to update My VZW XS MAX from > > > iOS12.4.1 to WhatEver is the Latest iOS13 iteration. > > > > > > (I Presume) > > > it's because I didn't Update Past iOS12, > > as if I did "they" could say that the > > > BugFixes were Resolved in a Future iOS > > update of iOS13, but since I refused to > > > UpdatePast iOS12.4.1, I can't Be Denied TelephoneSupport from > > > AppleAccessibility on My VZW XS MAX At 06:30 PM 8/29/2020, you wrote: > > > >I just hope the device you don't have it on, you won't need help > > > &
Re: for Joshua
No problem with anyone here. I always update within a few days after an update has come out for the reasons others have stated. Sent from my iPhone > On Aug 30, 2020, at 8:53 PM, chalt...@gmail.com wrote: > > Thanks Sherry. Yes, I was agreeing with Shirley and disagreeing with Robin. > In fact, I assumed Shirley's response was directed at Robin's message, the > same message I was responding to. > > -- > Christopher (AKA CJ) > Chaltain at Gmail > >> -Original Message- >> From: viphone@googlegroups.com On Behalf >> Of sherrywells1...@gmail.com >> Sent: Sunday, August 30, 2020 1:55 PM >> To: viphone@googlegroups.com >> Subject: RE: for Joshua >> >> Christopher wasn't saying he didn't believe you. He was saying he didn't >> know >> why you would think Apple could not refuse to help you unless you were on a >> more current version. Reread his post more carefully. >> >> Sherry Wells >> >> -Original Message- >> From: viphone@googlegroups.com On Behalf >> Of Shirley Baker >> Sent: Sunday, August 30, 2020 2:00 PM >> To: viphone@googlegroups.com >> Subject: Re: for Joshua >> >> I didn't think it up. This is what they told me and I can't help what your >> opinion >> might be but this particular person would not help me unless I updated my >> phone >> at that time. Whatever you believe is not my problem. I'm just telling you >> what >> that person said so I did what they told me to do and have ever since. >> >> Sent from my iPhone >> >>>> On Aug 30, 2020, at 10:33 AM, chalt...@gmail.com wrote: >>> >>> I'm not sure why you think Apple can't deny you telephone support for an >>> older >> unsupported version of IOS. You may be getting telephone support for now, but >> I doubt it'll last forever. I'm pretty sure Apple isn't releasing security >> updates for >> 12.4.1 any more either. Plus there's nothing that says app developers have to >> continue to support 12.4.1. >>> >>> -- >>> Christopher (AKA CJ) >>> Chaltain at Gmail >>> >>>> -Original Message- >>>> From: viphone@googlegroups.com On >> Behalf >>>> Of Robin >>>> Sent: Saturday, August 29, 2020 8:59 PM >>>> To: viphone@googlegroups.com >>>> Subject: Re: for Joshua >>>> >>>> Okay, Ms. Shirley >>>> After I received Your MessagePosting, which AppearsBelow this >>>> MessagePosting of Mine, I decided to Call Apple's >>>> AppleAccessibility TelephoneSupport @ 877-204-3930, To InQuire about >>>> "what" you said, & I was informed that I wouldn't Be Denied >>>> TelephoneSupport from Apple's AppleAccessibility because I refused >>>> to update My VZW XS MAX from >>>> iOS12.4.1 to WhatEver is the Latest iOS13 iteration. >>>> >>>> (I Presume) >>>> it's because I didn't Update Past iOS12, as if I did "they" >>>> could say that the BugFixes were Resolved in a Future iOS update of >>>> iOS13, but since I refused to UpdatePast iOS12.4.1, I can't Be >>>> Denied TelephoneSupport from AppleAccessibility on My VZW XS MAX At >> 06:30 PM 8/29/2020, you wrote: >>>>> I just hope the device you don't have it on, you won't need help >>>>> from Apple Accessibility because they told me they require you to >>>>> have whatever device you're requesting help with, to be updated to >>>>> the latest version or they won't help you so every since they told >>>>> me that, I make sure my devices are all updated. >>>>> >>>>> Sent from my iPhone >>>>> >>>>>>> On Aug 29, 2020, at 4:52 PM, Robin wrote: >>>>>>> >>>>>>> You Ask? How will "I Know"? >>>>>>> If Ya ReadMyReplyMessagePosting to >>>>> ThisThread, I said, that I have Apple's iOS13 on My VZW 11PRO >>>>> PrimarilyBecause that is the iOS version that it was LaunchedWith, >>>>> but My VZW XS MAX wasn't, & Because of TheBugs >>>>> AssociatedWith iOS13, I Refuse to Update it >>>>> to iOS13, so it Remains on its Last Update, which is iOS12.4.1. >>>>>> MayBe just MayBe >>>>>> You're More TechSavy
RE: for Joshua
Thanks Sherry. Yes, I was agreeing with Shirley and disagreeing with Robin. In fact, I assumed Shirley's response was directed at Robin's message, the same message I was responding to. -- Christopher (AKA CJ) Chaltain at Gmail > -Original Message- > From: viphone@googlegroups.com On Behalf > Of sherrywells1...@gmail.com > Sent: Sunday, August 30, 2020 1:55 PM > To: viphone@googlegroups.com > Subject: RE: for Joshua > > Christopher wasn't saying he didn't believe you. He was saying he didn't know > why you would think Apple could not refuse to help you unless you were on a > more current version. Reread his post more carefully. > > Sherry Wells > > -Original Message- > From: viphone@googlegroups.com On Behalf > Of Shirley Baker > Sent: Sunday, August 30, 2020 2:00 PM > To: viphone@googlegroups.com > Subject: Re: for Joshua > > I didn't think it up. This is what they told me and I can't help what your > opinion > might be but this particular person would not help me unless I updated my > phone > at that time. Whatever you believe is not my problem. I'm just telling you > what > that person said so I did what they told me to do and have ever since. > > Sent from my iPhone > > > On Aug 30, 2020, at 10:33 AM, chalt...@gmail.com wrote: > > > > I'm not sure why you think Apple can't deny you telephone support for an > > older > unsupported version of IOS. You may be getting telephone support for now, but > I doubt it'll last forever. I'm pretty sure Apple isn't releasing security > updates for > 12.4.1 any more either. Plus there's nothing that says app developers have to > continue to support 12.4.1. > > > > -- > > Christopher (AKA CJ) > > Chaltain at Gmail > > > >> -Original Message- > >> From: viphone@googlegroups.com On > Behalf > >> Of Robin > >> Sent: Saturday, August 29, 2020 8:59 PM > >> To: viphone@googlegroups.com > >> Subject: Re: for Joshua > >> > >> Okay, Ms. Shirley > >> After I received Your MessagePosting, which AppearsBelow this > >> MessagePosting of Mine, I decided to Call Apple's > >> AppleAccessibility TelephoneSupport @ 877-204-3930, To InQuire about > >> "what" you said, & I was informed that I wouldn't Be Denied > >> TelephoneSupport from Apple's AppleAccessibility because I refused > >> to update My VZW XS MAX from > >> iOS12.4.1 to WhatEver is the Latest iOS13 iteration. > >> > >> (I Presume) > >> it's because I didn't Update Past iOS12, as if I did "they" > >> could say that the BugFixes were Resolved in a Future iOS update of > >> iOS13, but since I refused to UpdatePast iOS12.4.1, I can't Be > >> Denied TelephoneSupport from AppleAccessibility on My VZW XS MAX At > 06:30 PM 8/29/2020, you wrote: > >>> I just hope the device you don't have it on, you won't need help > >>> from Apple Accessibility because they told me they require you to > >>> have whatever device you're requesting help with, to be updated to > >>> the latest version or they won't help you so every since they told > >>> me that, I make sure my devices are all updated. > >>> > >>> Sent from my iPhone > >>> > >>>>> On Aug 29, 2020, at 4:52 PM, Robin wrote: > >>>>> > >>>>> You Ask? How will "I Know"? > >>>>> If Ya ReadMyReplyMessagePosting to > >>> ThisThread, I said, that I have Apple's iOS13 on My VZW 11PRO > >>> PrimarilyBecause that is the iOS version that it was LaunchedWith, > >>> but My VZW XS MAX wasn't, & Because of TheBugs > >>> AssociatedWith iOS13, I Refuse to Update it > >>> to iOS13, so it Remains on its Last Update, which is iOS12.4.1. > >>>> MayBe just MayBe > >>>> You're More TechSavy than I am. Yeah, > >>> that's MostLikely TheCase, as I'm not that TechSavy > >>>> > >>>> MyApologies, if this MessagePosting offends, as it isn't intended ToDoSo. > >>>> I'm just Stating-the-Facts, as "I See" them > >>>> > >>>> Blessin's to Those on ThisThread > >>>> At 01:56 PM 8/29/2020, you wrote: > >>>>> It's not that bad. How would you know how > >>> bad it is since you haven't updated?
RE: for Joshua
Apple already aggressively pushes out updates to their devices, for example, within a few days of a release, you won't be able to roll back to a previous release. Plus they drop pushing out security updates once a newer release has been deployed. With the adoption rate Apple has with new releases, I doubt it would be a serious PR issue for them to stop providing customer support for a release that's been superseded by a newer release that's still getting security updates. Apple wouldn't be the first company to ask you to update to a newer version of software before providing you support. Sometimes this is legitimate, since newer versions of the software will contain fixes for issues being reported to customer support. . You may be able to stay on IOS 12.4.1, but there's no guarantee that Apple will continue to provide customer support for an unsupported version of IOS. Don't get me wrong, I don't have a problem with you staying on IOS 12.4.1 as long as you want. My only reason for posting is to let others know that there's no obligation or guarantee from Apple to support 12.4.1 forever. Plus, anyone who stays on IOS 12.4.1 will be missing out on security patches and may not get support from app developers on 12.4.1. I'm totally on board with people having the right to choose, as long as they're given accurate information to make that choice. -- Christopher (AKA CJ) Chaltain at Gmail > -Original Message- > From: viphone@googlegroups.com On Behalf > Of Robin > Sent: Sunday, August 30, 2020 4:04 PM > To: viphone@googlegroups.com > Subject: RE: for Joshua > > Oh, but "They" Because I have AppleCare+ on it, & it would be a Bad PR Move > not to Support it. Pressuring a Consumer to Update a SoftwareVersion, > which > "They" (Apple) deemed ReadyFor PublicRelease . It's MyRight, as a Consumer > Not to Update MyDevice'sSoftware & there isn't AnyWhere in AppleCare+ that > Sayz that I must, & I Called & CheckedWith Apple's AppleAccessibility > TelephoneSupport, & "They" > indicated that I wouldn't Be Denied & that's that. > > At 08:33 AM 8/30/2020, you wrote: > >I'm not sure why you think Apple can't deny you telephone support for > >an older unsupported version of IOS. You may be getting telephone > >support for now, but I doubt it'll last forever. > >I'm pretty sure Apple isn't releasing security updates for 12.4.1 any > >more either. Plus there's nothing that says app developers have to > >continue to support 12.4.1. > > > >-- > >Christopher (AKA CJ) > >Chaltain at Gmail > > > > > -Original Message- > > > From: viphone@googlegroups.com On > Behalf > > > Of Robin > > > Sent: Saturday, August 29, 2020 8:59 PM > > > To: viphone@googlegroups.com > > > Subject: Re: for Joshua > > > > > > Okay, Ms. Shirley > > >After I received Your MessagePosting, which AppearsBelow this > > > MessagePosting of Mine, I decided to Call Apple's > > > AppleAccessibility TelephoneSupport @ 877-204-3930, To InQuire about > > > "what" you said, & I was informed that I wouldn't Be Denied > > > TelephoneSupport from Apple's AppleAccessibility because I refused > > > to update My VZW XS MAX from > > > iOS12.4.1 to WhatEver is the Latest iOS13 iteration. > > > > > > (I Presume) > > > it's because I didn't Update Past iOS12, > > as if I did "they" could say that the > > > BugFixes were Resolved in a Future iOS > > update of iOS13, but since I refused to > > > UpdatePast iOS12.4.1, I can't Be Denied TelephoneSupport from > > > AppleAccessibility on My VZW XS MAX At 06:30 PM 8/29/2020, you wrote: > > > >I just hope the device you don't have it on, you won't need help > > > >from Apple Accessibility because they told me they require you to > > > >have whatever device you're requesting help with, to be updated to > > > >the latest version or they won't help you so every since they told > > > >me that, I make sure my devices are all updated. > > > > > > > >Sent from my iPhone > > > > > > > > > On Aug 29, 2020, at 4:52 PM, Robin wrote: > > > > > > > > > > You Ask? How will "I Know"? > > > > > If Ya ReadMyReplyMessagePosting to > > > > ThisThread, I said, that I have Apple's iOS13 on My VZW 11PRO > > > > Prim
RE: for Joshua
But if you ask for assistance and the version of the OS is not currently the most up to date version available, They will ask you to update before completing the help you need. It would be part of the checking of the issues. -Original Message- From: viphone@googlegroups.com On Behalf Of Robin Sent: Monday, 31 August 2020 9:09 AM To: viphone@googlegroups.com Subject: RE: for Joshua Oh Yeah, ForGot: I know AppDevelopers aren't RequiredTo support OlderVersions of iOS: Not arguing with you on that Front. MoneyReader's AppDeveloper isn't supporting the LatestIteration of Apple's iOS, as its MobileApp, MoneyReader doesn't work on iOS13, but it does on iOS12. At 08:33 AM 8/30/2020, you wrote: >I'm not sure why you think Apple can't deny you telephone support for >an older unsupported version of IOS. You may be getting telephone >support for now, but I doubt it'll last forever. >I'm pretty sure Apple isn't releasing security updates for 12.4.1 any >more either. Plus there's nothing that says app developers have to >continue to support 12.4.1. > >-- >Christopher (AKA CJ) >Chaltain at Gmail > > > -Original Message- > > From: viphone@googlegroups.com On Behalf > > Of Robin > > Sent: Saturday, August 29, 2020 8:59 PM > > To: viphone@googlegroups.com > > Subject: Re: for Joshua > > > > Okay, Ms. Shirley > >After I received Your MessagePosting, which AppearsBelow this > > MessagePosting of Mine, I decided to Call Apple's > > AppleAccessibility TelephoneSupport @ 877-204-3930, To InQuire about > > "what" you said, & I was informed that I wouldn't Be Denied > > TelephoneSupport from Apple's AppleAccessibility because I refused > > to update My VZW XS MAX from > > iOS12.4.1 to WhatEver is the Latest iOS13 iteration. > > > > (I Presume) > > it's because I didn't Update Past iOS12, > as if I did "they" could say that the > > BugFixes were Resolved in a Future iOS > update of iOS13, but since I refused to > > UpdatePast iOS12.4.1, I can't Be Denied TelephoneSupport from > > AppleAccessibility on My VZW XS MAX At 06:30 PM 8/29/2020, you wrote: > > >I just hope the device you don't have it on, you won't need help > > >from Apple Accessibility because they told me they require you to > > >have whatever device you're requesting help with, to be updated to > > >the latest version or they won't help you so every since they told > > >me that, I make sure my devices are all updated. > > > > > >Sent from my iPhone > > > > > > > On Aug 29, 2020, at 4:52 PM, Robin wrote: > > > > > > > > You Ask? How will "I Know"? > > > > If Ya ReadMyReplyMessagePosting to > > > ThisThread, I said, that I have Apple's iOS13 on My VZW 11PRO > > > PrimarilyBecause that is the iOS version that it was LaunchedWith, > > > but My VZW XS MAX wasn't, & Because of TheBugs > > > AssociatedWith iOS13, I Refuse to Update it > > > to iOS13, so it Remains on its Last Update, which is iOS12.4.1. > > > > MayBe just MayBe > > > > You're More TechSavy than I am. Yeah, > > > that's MostLikely TheCase, as I'm not that TechSavy > > > > > > > > MyApologies, if this MessagePosting > offends, as it isn't intended ToDoSo. > > > > I'm just Stating-the-Facts, as "I See" them > > > > > > > > Blessin's to Those on ThisThread At 01:56 PM 8/29/2020, you > > > > wrote: > > > >> It's not that bad. How would you know how > > > bad it is since you haven't updated? Some people are just > > > unnecessarily paranoid.It's not that bad. > > > >> > > > >> Sent from my iPhone > > > >> > > > >> > On Aug 29, 2020, at 3:31 PM, Robin wrote: > > > >> > > > > >> > Well, TheBigDeal is iOS13 IS Buggy, > > > which is "Why" I Refuse to Update My VZW XS MAX, as it's going to > > > Stay ON iOS12.4.1, which is the iOS version it was when I > > > Purchased it, & I am PrivyTo TheBugs AssociatedWith > > > iOS13 because "They" are present on My VZW 11PRO, & that > > > MobileDevice is ON AutomaticUpdates (so far). It's TheUser'sChoice > > > To Update or Not > > > >> > At 01:13 PM 8/29/2020, you wrote: > > >
RE: for Joshua
Oh Yeah, ForGot: I know AppDevelopers aren't RequiredTo support OlderVersions of iOS: Not arguing with you on that Front. MoneyReader's AppDeveloper isn't supporting the LatestIteration of Apple's iOS, as its MobileApp, MoneyReader doesn't work on iOS13, but it does on iOS12. At 08:33 AM 8/30/2020, you wrote: I'm not sure why you think Apple can't deny you telephone support for an older unsupported version of IOS. You may be getting telephone support for now, but I doubt it'll last forever. I'm pretty sure Apple isn't releasing security updates for 12.4.1 any more either. Plus there's nothing that says app developers have to continue to support 12.4.1. -- Christopher (AKA CJ) Chaltain at Gmail > -Original Message- > From: viphone@googlegroups.com On Behalf > Of Robin > Sent: Saturday, August 29, 2020 8:59 PM > To: viphone@googlegroups.com > Subject: Re: for Joshua > > Okay, Ms. Shirley >After I received Your MessagePosting, which AppearsBelow this > MessagePosting of Mine, I decided to Call Apple's AppleAccessibility > TelephoneSupport @ 877-204-3930, To InQuire about "what" you said, & I was > informed that I wouldn't Be Denied TelephoneSupport from Apple's > AppleAccessibility because I refused to update My VZW XS MAX from > iOS12.4.1 to WhatEver is the Latest iOS13 iteration. > > (I Presume) > it's because I didn't Update Past iOS12, as if I did "they" could say that the > BugFixes were Resolved in a Future iOS update of iOS13, but since I refused to > UpdatePast iOS12.4.1, I can't Be Denied TelephoneSupport from > AppleAccessibility on My VZW XS MAX At 06:30 PM 8/29/2020, you wrote: > >I just hope the device you don't have it on, you won't need help from > >Apple Accessibility because they told me they require you to have > >whatever device you're requesting help with, to be updated to the > >latest version or they won't help you so every since they told me that, > >I make sure my devices are all updated. > > > >Sent from my iPhone > > > > > On Aug 29, 2020, at 4:52 PM, Robin wrote: > > > > > > You Ask? How will "I Know"? > > > If Ya ReadMyReplyMessagePosting to > > ThisThread, I said, that I have Apple's iOS13 on My VZW 11PRO > > PrimarilyBecause that is the iOS version that it was LaunchedWith, but > > My VZW XS MAX wasn't, & Because of TheBugs > > AssociatedWith iOS13, I Refuse to Update it > > to iOS13, so it Remains on its Last Update, which is iOS12.4.1. > > > MayBe just MayBe > > > You're More TechSavy than I am. Yeah, > > that's MostLikely TheCase, as I'm not that TechSavy > > > > > > MyApologies, if this MessagePosting offends, as it isn't intended ToDoSo. > > > I'm just Stating-the-Facts, as "I See" them > > > > > > Blessin's to Those on ThisThread > > > At 01:56 PM 8/29/2020, you wrote: > > >> It's not that bad. How would you know how > > bad it is since you haven't updated? Some people are just > > unnecessarily paranoid.It's not that bad. > > >> > > >> Sent from my iPhone > > >> > > >> > On Aug 29, 2020, at 3:31 PM, Robin wrote: > > >> > > > >> > Well, TheBigDeal is iOS13 IS Buggy, > > which is "Why" I Refuse to Update My VZW XS MAX, as it's going to > > Stay ON iOS12.4.1, which is the iOS version it was when I Purchased > > it, & I am PrivyTo TheBugs AssociatedWith > > iOS13 because "They" are present on My VZW 11PRO, & that MobileDevice > > is ON AutomaticUpdates (so far). It's TheUser'sChoice To Update or Not > > >> > At 01:13 PM 8/29/2020, you wrote: > > >> >> You can turn automatic update off but I > > don't see what the big deal is with not updating. > > >> >> > > >> >> Sent from my iPhone > > >> >> > > >> >> > On Aug 29, 2020, at 7:45 AM, Joshua > > Hendrickson wrote: > > >> >> > > > >> >> > ï»Ã šÃ‚¿Well, the good news is, I > > don't really mind the new update like I > > >> >> > thought I would. The only reason why I updated, was it seemed > > >> >> > like apple did the update, and I had to enter in my touch ID. > > >> >> > I didn't have the option of saying later. There is this weird > > >
RE: for Joshua
Oh, but "They" Because I have AppleCare+ on it, & it would be a Bad PR Move not to Support it. Pressuring a Consumer to Update a SoftwareVersion, which "They" (Apple) deemed ReadyFor PublicRelease . It's MyRight, as a Consumer Not to Update MyDevice'sSoftware & there isn't AnyWhere in AppleCare+ that Sayz that I must, & I Called & CheckedWith Apple's AppleAccessibility TelephoneSupport, & "They" indicated that I wouldn't Be Denied & that's that. At 08:33 AM 8/30/2020, you wrote: I'm not sure why you think Apple can't deny you telephone support for an older unsupported version of IOS. You may be getting telephone support for now, but I doubt it'll last forever. I'm pretty sure Apple isn't releasing security updates for 12.4.1 any more either. Plus there's nothing that says app developers have to continue to support 12.4.1. -- Christopher (AKA CJ) Chaltain at Gmail > -Original Message- > From: viphone@googlegroups.com On Behalf > Of Robin > Sent: Saturday, August 29, 2020 8:59 PM > To: viphone@googlegroups.com > Subject: Re: for Joshua > > Okay, Ms. Shirley >After I received Your MessagePosting, which AppearsBelow this > MessagePosting of Mine, I decided to Call Apple's AppleAccessibility > TelephoneSupport @ 877-204-3930, To InQuire about "what" you said, & I was > informed that I wouldn't Be Denied TelephoneSupport from Apple's > AppleAccessibility because I refused to update My VZW XS MAX from > iOS12.4.1 to WhatEver is the Latest iOS13 iteration. > > (I Presume) > it's because I didn't Update Past iOS12, as if I did "they" could say that the > BugFixes were Resolved in a Future iOS update of iOS13, but since I refused to > UpdatePast iOS12.4.1, I can't Be Denied TelephoneSupport from > AppleAccessibility on My VZW XS MAX At 06:30 PM 8/29/2020, you wrote: > >I just hope the device you don't have it on, you won't need help from > >Apple Accessibility because they told me they require you to have > >whatever device you're requesting help with, to be updated to the > >latest version or they won't help you so every since they told me that, > >I make sure my devices are all updated. > > > >Sent from my iPhone > > > > > On Aug 29, 2020, at 4:52 PM, Robin wrote: > > > > > > You Ask? How will "I Know"? > > > If Ya ReadMyReplyMessagePosting to > > ThisThread, I said, that I have Apple's iOS13 on My VZW 11PRO > > PrimarilyBecause that is the iOS version that it was LaunchedWith, but > > My VZW XS MAX wasn't, & Because of TheBugs > > AssociatedWith iOS13, I Refuse to Update it > > to iOS13, so it Remains on its Last Update, which is iOS12.4.1. > > > MayBe just MayBe > > > You're More TechSavy than I am. Yeah, > > that's MostLikely TheCase, as I'm not that TechSavy > > > > > > MyApologies, if this MessagePosting offends, as it isn't intended ToDoSo. > > > I'm just Stating-the-Facts, as "I See" them > > > > > > Blessin's to Those on ThisThread > > > At 01:56 PM 8/29/2020, you wrote: > > >> It's not that bad. How would you know how > > bad it is since you haven't updated? Some people are just > > unnecessarily paranoid.It's not that bad. > > >> > > >> Sent from my iPhone > > >> > > >> > On Aug 29, 2020, at 3:31 PM, Robin wrote: > > >> > > > >> > Well, TheBigDeal is iOS13 IS Buggy, > > which is "Why" I Refuse to Update My VZW XS MAX, as it's going to > > Stay ON iOS12.4.1, which is the iOS version it was when I Purchased > > it, & I am PrivyTo TheBugs AssociatedWith > > iOS13 because "They" are present on My VZW 11PRO, & that MobileDevice > > is ON AutomaticUpdates (so far). It's TheUser'sChoice To Update or Not > > >> > At 01:13 PM 8/29/2020, you wrote: > > >> >> You can turn automatic update off but I > > don't see what the big deal is with not updating. > > >> >> > > >> >> Sent from my iPhone > > >> >> > > >> >> > On Aug 29, 2020, at 7:45 AM, Joshua > > Hendrickson wrote: > > >> >> > > > >> >> > ï»Ã šÃ‚¿Well, the good news is, I > > don't really mind the new update like I > > >> >> > thought I would. The o
Re: for Joshua
The only reason I can think of why they may have said this, maybe what I was needing to be done at the time required an update but whatever the reason, it doesn't matter for me anymore, as I will always keep my phone updated. End of conversation from me after this. Sent from my iPhone > On Aug 30, 2020, at 1:54 PM, sherrywells1...@gmail.com wrote: > > Christopher wasn't saying he didn't believe you. He was saying he didn't > know why you would think Apple could not refuse to help you unless you were > on a more current version. Reread his post more carefully. > > Sherry Wells > > -Original Message- > From: viphone@googlegroups.com On Behalf Of > Shirley Baker > Sent: Sunday, August 30, 2020 2:00 PM > To: viphone@googlegroups.com > Subject: Re: for Joshua > > I didn't think it up. This is what they told me and I can't help what your > opinion might be but this particular person would not help me unless I > updated my phone at that time. Whatever you believe is not my problem. I'm > just telling you what that person said so I did what they told me to do and > have ever since. > > Sent from my iPhone > >> On Aug 30, 2020, at 10:33 AM, chalt...@gmail.com wrote: >> >> I'm not sure why you think Apple can't deny you telephone support for an >> older unsupported version of IOS. You may be getting telephone support for >> now, but I doubt it'll last forever. I'm pretty sure Apple isn't releasing >> security updates for 12.4.1 any more either. Plus there's nothing that says >> app developers have to continue to support 12.4.1. >> >> -- >> Christopher (AKA CJ) >> Chaltain at Gmail >> >>> -Original Message- >>> From: viphone@googlegroups.com On Behalf >>> Of Robin >>> Sent: Saturday, August 29, 2020 8:59 PM >>> To: viphone@googlegroups.com >>> Subject: Re: for Joshua >>> >>> Okay, Ms. Shirley >>> After I received Your MessagePosting, which AppearsBelow this >>> MessagePosting of Mine, I decided to Call Apple's >>> AppleAccessibility TelephoneSupport @ 877-204-3930, To InQuire about >>> "what" you said, & I was informed that I wouldn't Be Denied >>> TelephoneSupport from Apple's AppleAccessibility because I refused >>> to update My VZW XS MAX from >>> iOS12.4.1 to WhatEver is the Latest iOS13 iteration. >>> >>> (I Presume) >>> it's because I didn't Update Past iOS12, as if I did "they" >>> could say that the BugFixes were Resolved in a Future iOS update of >>> iOS13, but since I refused to UpdatePast iOS12.4.1, I can't Be >>> Denied TelephoneSupport from AppleAccessibility on My VZW XS MAX At 06:30 >>> PM 8/29/2020, you wrote: >>>> I just hope the device you don't have it on, you won't need help >>>> from Apple Accessibility because they told me they require you to >>>> have whatever device you're requesting help with, to be updated to >>>> the latest version or they won't help you so every since they told >>>> me that, I make sure my devices are all updated. >>>> >>>> Sent from my iPhone >>>> >>>>>> On Aug 29, 2020, at 4:52 PM, Robin wrote: >>>>>> >>>>>> You Ask? How will "I Know"? >>>>>> If Ya ReadMyReplyMessagePosting to >>>> ThisThread, I said, that I have Apple's iOS13 on My VZW 11PRO >>>> PrimarilyBecause that is the iOS version that it was LaunchedWith, >>>> but My VZW XS MAX wasn't, & Because of TheBugs >>>> AssociatedWith iOS13, I Refuse to Update it >>>> to iOS13, so it Remains on its Last Update, which is iOS12.4.1. >>>>> MayBe just MayBe >>>>> You're More TechSavy than I am. Yeah, >>>> that's MostLikely TheCase, as I'm not that TechSavy >>>>> >>>>> MyApologies, if this MessagePosting offends, as it isn't intended ToDoSo. >>>>> I'm just Stating-the-Facts, as "I See" them >>>>> >>>>> Blessin's to Those on ThisThread >>>>> At 01:56 PM 8/29/2020, you wrote: >>>>>> It's not that bad. How would you know how >>>> bad it is since you haven't updated? Some people are just >>>> unnecessarily paranoid.It's not that bad. >>>>>> >>>>>>
RE: for Joshua
I agree, Shirley I'm sorry you had that experience too. I'm just saying I'm not surprised because the tech support folks would tend to think your problem was due to having an old version of the software. I would think most problems could be resolved no matter the version but I'm sure there are some things that are harder to troubleshoot if one is not current. Sherry Wells -Original Message- From: viphone@googlegroups.com On Behalf Of Joshua Hendrickson Sent: Sunday, August 30, 2020 3:04 PM To: viphone@googlegroups.com Subject: Re: for Joshua I've never heard of apple accessibility refusing to help you if you weren't up to date. I didn't update my iPhone for almost a year and I had no trouble having apple help me with any issues. Shirley Sorry you had that experience. On 8/30/20, sherrywells1...@gmail.com wrote: > Christopher wasn't saying he didn't believe you. He was saying he > didn't know why you would think Apple could not refuse to help you > unless you were on a more current version. Reread his post more carefully. > > Sherry Wells > > -Original Message- > From: viphone@googlegroups.com On Behalf Of > Shirley Baker > Sent: Sunday, August 30, 2020 2:00 PM > To: viphone@googlegroups.com > Subject: Re: for Joshua > > I didn't think it up. This is what they told me and I can't help what > your opinion might be but this particular person would not help me > unless I updated my phone at that time. Whatever you believe is not my > problem. I'm just telling you what that person said so I did what they > told me to do and have ever since. > > Sent from my iPhone > >> On Aug 30, 2020, at 10:33 AM, chalt...@gmail.com wrote: >> >> I'm not sure why you think Apple can't deny you telephone support >> for an older unsupported version of IOS. You may be getting telephone >> support for now, but I doubt it'll last forever. I'm pretty sure >> Apple isn't releasing security updates for 12.4.1 any more either. >> Plus there's nothing that says app developers have to continue to support >> 12.4.1. >> >> -- >> Christopher (AKA CJ) >> Chaltain at Gmail >> >>> -Original Message- >>> From: viphone@googlegroups.com On Behalf >>> Of Robin >>> Sent: Saturday, August 29, 2020 8:59 PM >>> To: viphone@googlegroups.com >>> Subject: Re: for Joshua >>> >>> Okay, Ms. Shirley >>> After I received Your MessagePosting, which AppearsBelow this >>> MessagePosting of Mine, I decided to Call Apple's >>> AppleAccessibility TelephoneSupport @ 877-204-3930, To InQuire about >>> "what" you said, & I was informed that I wouldn't Be Denied >>> TelephoneSupport from Apple's AppleAccessibility because I refused >>> to update My VZW XS MAX from >>> iOS12.4.1 to WhatEver is the Latest iOS13 iteration. >>> >>> (I Presume) >>> it's because I didn't Update Past iOS12, as if I did "they" >>> could say that the BugFixes were Resolved in a Future iOS update >>> of iOS13, but since I refused to UpdatePast iOS12.4.1, I can't Be >>> Denied TelephoneSupport from AppleAccessibility on My VZW XS MAX At >>> 06:30 PM 8/29/2020, you wrote: >>>> I just hope the device you don't have it on, you won't need help >>>> from Apple Accessibility because they told me they require you to >>>> have whatever device you're requesting help with, to be updated to >>>> the latest version or they won't help you so every since they told >>>> me that, I make sure my devices are all updated. >>>> >>>> Sent from my iPhone >>>> >>>>>> On Aug 29, 2020, at 4:52 PM, Robin wrote: >>>>>> >>>>>> You Ask? How will "I Know"? >>>>>> If Ya ReadMyReplyMessagePosting to >>>> ThisThread, I said, that I have Apple's iOS13 on My VZW 11PRO >>>> PrimarilyBecause that is the iOS version that it was LaunchedWith, >>>> but My VZW XS MAX wasn't, & Because of TheBugs >>>> AssociatedWith iOS13, I Refuse to Update it >>>> to iOS13, so it Remains on its Last Update, which is iOS12.4.1. >>>>> MayBe just MayBe >>>>> You're More TechSavy than I am. Yeah, >>>> that's MostLikely TheCase, as I'm not that TechSavy >>>>> >>>>> MyApologies, if this MessagePosting offends, as it is
Re: for Joshua
I've never heard of apple accessibility refusing to help you if you weren't up to date. I didn't update my iPhone for almost a year and I had no trouble having apple help me with any issues. Shirley Sorry you had that experience. On 8/30/20, sherrywells1...@gmail.com wrote: > Christopher wasn't saying he didn't believe you. He was saying he didn't > know why you would think Apple could not refuse to help you unless you were > on a more current version. Reread his post more carefully. > > Sherry Wells > > -Original Message- > From: viphone@googlegroups.com On Behalf Of > Shirley Baker > Sent: Sunday, August 30, 2020 2:00 PM > To: viphone@googlegroups.com > Subject: Re: for Joshua > > I didn't think it up. This is what they told me and I can't help what your > opinion might be but this particular person would not help me unless I > updated my phone at that time. Whatever you believe is not my problem. I'm > just telling you what that person said so I did what they told me to do and > have ever since. > > Sent from my iPhone > >> On Aug 30, 2020, at 10:33 AM, chalt...@gmail.com wrote: >> >> I'm not sure why you think Apple can't deny you telephone support for an >> older unsupported version of IOS. You may be getting telephone support for >> now, but I doubt it'll last forever. I'm pretty sure Apple isn't releasing >> security updates for 12.4.1 any more either. Plus there's nothing that >> says app developers have to continue to support 12.4.1. >> >> -- >> Christopher (AKA CJ) >> Chaltain at Gmail >> >>> -Original Message- >>> From: viphone@googlegroups.com On Behalf >>> Of Robin >>> Sent: Saturday, August 29, 2020 8:59 PM >>> To: viphone@googlegroups.com >>> Subject: Re: for Joshua >>> >>> Okay, Ms. Shirley >>> After I received Your MessagePosting, which AppearsBelow this >>> MessagePosting of Mine, I decided to Call Apple's >>> AppleAccessibility TelephoneSupport @ 877-204-3930, To InQuire about >>> "what" you said, & I was informed that I wouldn't Be Denied >>> TelephoneSupport from Apple's AppleAccessibility because I refused >>> to update My VZW XS MAX from >>> iOS12.4.1 to WhatEver is the Latest iOS13 iteration. >>> >>> (I Presume) >>> it's because I didn't Update Past iOS12, as if I did "they" >>> could say that the BugFixes were Resolved in a Future iOS update of >>> iOS13, but since I refused to UpdatePast iOS12.4.1, I can't Be >>> Denied TelephoneSupport from AppleAccessibility on My VZW XS MAX At 06:30 >>> PM 8/29/2020, you wrote: >>>> I just hope the device you don't have it on, you won't need help >>>> from Apple Accessibility because they told me they require you to >>>> have whatever device you're requesting help with, to be updated to >>>> the latest version or they won't help you so every since they told >>>> me that, I make sure my devices are all updated. >>>> >>>> Sent from my iPhone >>>> >>>>>> On Aug 29, 2020, at 4:52 PM, Robin wrote: >>>>>> >>>>>> You Ask? How will "I Know"? >>>>>> If Ya ReadMyReplyMessagePosting to >>>> ThisThread, I said, that I have Apple's iOS13 on My VZW 11PRO >>>> PrimarilyBecause that is the iOS version that it was LaunchedWith, >>>> but My VZW XS MAX wasn't, & Because of TheBugs >>>> AssociatedWith iOS13, I Refuse to Update it >>>> to iOS13, so it Remains on its Last Update, which is iOS12.4.1. >>>>> MayBe just MayBe >>>>> You're More TechSavy than I am. Yeah, >>>> that's MostLikely TheCase, as I'm not that TechSavy >>>>> >>>>> MyApologies, if this MessagePosting offends, as it isn't intended >>>>> ToDoSo. >>>>> I'm just Stating-the-Facts, as "I See" them >>>>> >>>>> Blessin's to Those on ThisThread >>>>> At 01:56 PM 8/29/2020, you wrote: >>>>>> It's not that bad. How would you know how >>>> bad it is since you haven't updated? Some people are just >>>> unnecessarily paranoid.It's not that bad. >>>>>> >>>>>> Sent from my iPhone >>>>>> >>>>>>> On Aug 29, 2020, at
RE: for Joshua
Christopher wasn't saying he didn't believe you. He was saying he didn't know why you would think Apple could not refuse to help you unless you were on a more current version. Reread his post more carefully. Sherry Wells -Original Message- From: viphone@googlegroups.com On Behalf Of Shirley Baker Sent: Sunday, August 30, 2020 2:00 PM To: viphone@googlegroups.com Subject: Re: for Joshua I didn't think it up. This is what they told me and I can't help what your opinion might be but this particular person would not help me unless I updated my phone at that time. Whatever you believe is not my problem. I'm just telling you what that person said so I did what they told me to do and have ever since. Sent from my iPhone > On Aug 30, 2020, at 10:33 AM, chalt...@gmail.com wrote: > > I'm not sure why you think Apple can't deny you telephone support for an > older unsupported version of IOS. You may be getting telephone support for > now, but I doubt it'll last forever. I'm pretty sure Apple isn't releasing > security updates for 12.4.1 any more either. Plus there's nothing that says > app developers have to continue to support 12.4.1. > > -- > Christopher (AKA CJ) > Chaltain at Gmail > >> -Original Message- >> From: viphone@googlegroups.com On Behalf >> Of Robin >> Sent: Saturday, August 29, 2020 8:59 PM >> To: viphone@googlegroups.com >> Subject: Re: for Joshua >> >> Okay, Ms. Shirley >> After I received Your MessagePosting, which AppearsBelow this >> MessagePosting of Mine, I decided to Call Apple's >> AppleAccessibility TelephoneSupport @ 877-204-3930, To InQuire about >> "what" you said, & I was informed that I wouldn't Be Denied >> TelephoneSupport from Apple's AppleAccessibility because I refused >> to update My VZW XS MAX from >> iOS12.4.1 to WhatEver is the Latest iOS13 iteration. >> >> (I Presume) >> it's because I didn't Update Past iOS12, as if I did "they" >> could say that the BugFixes were Resolved in a Future iOS update of >> iOS13, but since I refused to UpdatePast iOS12.4.1, I can't Be >> Denied TelephoneSupport from AppleAccessibility on My VZW XS MAX At 06:30 PM >> 8/29/2020, you wrote: >>> I just hope the device you don't have it on, you won't need help >>> from Apple Accessibility because they told me they require you to >>> have whatever device you're requesting help with, to be updated to >>> the latest version or they won't help you so every since they told >>> me that, I make sure my devices are all updated. >>> >>> Sent from my iPhone >>> >>>>> On Aug 29, 2020, at 4:52 PM, Robin wrote: >>>>> >>>>> You Ask? How will "I Know"? >>>>> If Ya ReadMyReplyMessagePosting to >>> ThisThread, I said, that I have Apple's iOS13 on My VZW 11PRO >>> PrimarilyBecause that is the iOS version that it was LaunchedWith, >>> but My VZW XS MAX wasn't, & Because of TheBugs >>> AssociatedWith iOS13, I Refuse to Update it >>> to iOS13, so it Remains on its Last Update, which is iOS12.4.1. >>>> MayBe just MayBe >>>> You're More TechSavy than I am. Yeah, >>> that's MostLikely TheCase, as I'm not that TechSavy >>>> >>>> MyApologies, if this MessagePosting offends, as it isn't intended ToDoSo. >>>> I'm just Stating-the-Facts, as "I See" them >>>> >>>> Blessin's to Those on ThisThread >>>> At 01:56 PM 8/29/2020, you wrote: >>>>> It's not that bad. How would you know how >>> bad it is since you haven't updated? Some people are just >>> unnecessarily paranoid.It's not that bad. >>>>> >>>>> Sent from my iPhone >>>>> >>>>>> On Aug 29, 2020, at 3:31 PM, Robin wrote: >>>>>> >>>>>> Well, TheBigDeal is iOS13 IS Buggy, >>> which is "Why" I Refuse to Update My VZW XS MAX, as it's going to >>> Stay ON iOS12.4.1, which is the iOS version it was when I >>> Purchased it, & I am PrivyTo TheBugs AssociatedWith >>> iOS13 because "They" are present on My VZW 11PRO, & that >>> MobileDevice is ON AutomaticUpdates (so far). It's TheUser'sChoice >>> To Update or Not >>>>>> At 01:13 PM 8/29/2020, you wrote: >>>>>
Re: for Joshua
I didn't think it up. This is what they told me and I can't help what your opinion might be but this particular person would not help me unless I updated my phone at that time. Whatever you believe is not my problem. I'm just telling you what that person said so I did what they told me to do and have ever since. Sent from my iPhone > On Aug 30, 2020, at 10:33 AM, chalt...@gmail.com wrote: > > I'm not sure why you think Apple can't deny you telephone support for an > older unsupported version of IOS. You may be getting telephone support for > now, but I doubt it'll last forever. I'm pretty sure Apple isn't releasing > security updates for 12.4.1 any more either. Plus there's nothing that says > app developers have to continue to support 12.4.1. > > -- > Christopher (AKA CJ) > Chaltain at Gmail > >> -Original Message- >> From: viphone@googlegroups.com On Behalf >> Of Robin >> Sent: Saturday, August 29, 2020 8:59 PM >> To: viphone@googlegroups.com >> Subject: Re: for Joshua >> >> Okay, Ms. Shirley >> After I received Your MessagePosting, which AppearsBelow this >> MessagePosting of Mine, I decided to Call Apple's AppleAccessibility >> TelephoneSupport @ 877-204-3930, To InQuire about "what" you said, & I was >> informed that I wouldn't Be Denied TelephoneSupport from Apple's >> AppleAccessibility because I refused to update My VZW XS MAX from >> iOS12.4.1 to WhatEver is the Latest iOS13 iteration. >> >> (I Presume) >> it's because I didn't Update Past iOS12, as if I did "they" could say >> that the >> BugFixes were Resolved in a Future iOS update of iOS13, but since I >> refused to >> UpdatePast iOS12.4.1, I can't Be Denied TelephoneSupport from >> AppleAccessibility on My VZW XS MAX At 06:30 PM 8/29/2020, you wrote: >>> I just hope the device you don't have it on, you won't need help from >>> Apple Accessibility because they told me they require you to have >>> whatever device you're requesting help with, to be updated to the >>> latest version or they won't help you so every since they told me that, >>> I make sure my devices are all updated. >>> >>> Sent from my iPhone >>> >>>>> On Aug 29, 2020, at 4:52 PM, Robin wrote: >>>>> >>>>> You Ask? How will "I Know"? >>>>> If Ya ReadMyReplyMessagePosting to >>> ThisThread, I said, that I have Apple's iOS13 on My VZW 11PRO >>> PrimarilyBecause that is the iOS version that it was LaunchedWith, but >>> My VZW XS MAX wasn't, & Because of TheBugs >>> AssociatedWith iOS13, I Refuse to Update it >>> to iOS13, so it Remains on its Last Update, which is iOS12.4.1. >>>> MayBe just MayBe >>>> You're More TechSavy than I am. Yeah, >>> that's MostLikely TheCase, as I'm not that TechSavy >>>> >>>> MyApologies, if this MessagePosting offends, as it isn't intended ToDoSo. >>>> I'm just Stating-the-Facts, as "I See" them >>>> >>>> Blessin's to Those on ThisThread >>>> At 01:56 PM 8/29/2020, you wrote: >>>>> It's not that bad. How would you know how >>> bad it is since you haven't updated? Some people are just >>> unnecessarily paranoid.It's not that bad. >>>>> >>>>> Sent from my iPhone >>>>> >>>>>> On Aug 29, 2020, at 3:31 PM, Robin wrote: >>>>>> >>>>>> Well, TheBigDeal is iOS13 IS Buggy, >>> which is "Why" I Refuse to Update My VZW XS MAX, as it's going to >>> Stay ON iOS12.4.1, which is the iOS version it was when I Purchased >>> it, & I am PrivyTo TheBugs AssociatedWith >>> iOS13 because "They" are present on My VZW 11PRO, & that MobileDevice >>> is ON AutomaticUpdates (so far). It's TheUser'sChoice To Update or Not >>>>>> At 01:13 PM 8/29/2020, you wrote: >>>>>>> You can turn automatic update off but I >>> don't see what the big deal is with not updating. >>>>>>> >>>>>>> Sent from my iPhone >>>>>>> >>>>>>>> On Aug 29, 2020, at 7:45 AM, Joshua >>> Hendrickson wrote: >>>>>>>> >>>>>>>> Well, the good news is, I >>> don'
RE: for Joshua
I'm not sure why you think Apple can't deny you telephone support for an older unsupported version of IOS. You may be getting telephone support for now, but I doubt it'll last forever. I'm pretty sure Apple isn't releasing security updates for 12.4.1 any more either. Plus there's nothing that says app developers have to continue to support 12.4.1. -- Christopher (AKA CJ) Chaltain at Gmail > -Original Message- > From: viphone@googlegroups.com On Behalf > Of Robin > Sent: Saturday, August 29, 2020 8:59 PM > To: viphone@googlegroups.com > Subject: Re: for Joshua > > Okay, Ms. Shirley >After I received Your MessagePosting, which AppearsBelow this > MessagePosting of Mine, I decided to Call Apple's AppleAccessibility > TelephoneSupport @ 877-204-3930, To InQuire about "what" you said, & I was > informed that I wouldn't Be Denied TelephoneSupport from Apple's > AppleAccessibility because I refused to update My VZW XS MAX from > iOS12.4.1 to WhatEver is the Latest iOS13 iteration. > > (I Presume) > it's because I didn't Update Past iOS12, as if I did "they" could say > that the > BugFixes were Resolved in a Future iOS update of iOS13, but since I refused > to > UpdatePast iOS12.4.1, I can't Be Denied TelephoneSupport from > AppleAccessibility on My VZW XS MAX At 06:30 PM 8/29/2020, you wrote: > >I just hope the device you don't have it on, you won't need help from > >Apple Accessibility because they told me they require you to have > >whatever device you're requesting help with, to be updated to the > >latest version or they won't help you so every since they told me that, > >I make sure my devices are all updated. > > > >Sent from my iPhone > > > > > On Aug 29, 2020, at 4:52 PM, Robin wrote: > > > > > > You Ask? How will "I Know"? > > > If Ya ReadMyReplyMessagePosting to > > ThisThread, I said, that I have Apple's iOS13 on My VZW 11PRO > > PrimarilyBecause that is the iOS version that it was LaunchedWith, but > > My VZW XS MAX wasn't, & Because of TheBugs > > AssociatedWith iOS13, I Refuse to Update it > > to iOS13, so it Remains on its Last Update, which is iOS12.4.1. > > > MayBe just MayBe > > > You're More TechSavy than I am. Yeah, > > that's MostLikely TheCase, as I'm not that TechSavy > > > > > > MyApologies, if this MessagePosting offends, as it isn't intended ToDoSo. > > > I'm just Stating-the-Facts, as "I See" them > > > > > > Blessin's to Those on ThisThread > > > At 01:56 PM 8/29/2020, you wrote: > > >> It's not that bad. How would you know how > > bad it is since you haven't updated? Some people are just > > unnecessarily paranoid.It's not that bad. > > >> > > >> Sent from my iPhone > > >> > > >> > On Aug 29, 2020, at 3:31 PM, Robin wrote: > > >> > > > >> > Well, TheBigDeal is iOS13 IS Buggy, > > which is "Why" I Refuse to Update My VZW XS MAX, as it's going to > > Stay ON iOS12.4.1, which is the iOS version it was when I Purchased > > it, & I am PrivyTo TheBugs AssociatedWith > > iOS13 because "They" are present on My VZW 11PRO, & that MobileDevice > > is ON AutomaticUpdates (so far). It's TheUser'sChoice To Update or Not > > >> > At 01:13 PM 8/29/2020, you wrote: > > >> >> You can turn automatic update off but I > > don't see what the big deal is with not updating. > > >> >> > > >> >> Sent from my iPhone > > >> >> > > >> >> > On Aug 29, 2020, at 7:45 AM, Joshua > > Hendrickson wrote: > > >> >> > > > >> >> > Well, the good news is, I > > don't really mind the new update like I > > >> >> > thought I would. The only reason why I updated, was it seemed > > >> >> > like apple did the update, and I had to enter in my touch ID. > > >> >> > I didn't have the option of saying later. There is this weird > > >> >> > tapping thing that might happen when you update. You > > will feel it when you swipe on > > >> >> > the screen. Just call apple accessibility and they will help > > >> >> > you get rid of that. You won't be able to check the status > > >> >> > bar to see the batt
Re: for Joshua
MyBad & MyApologies: Thought "what" I was Talkin'About was "Clear". My VZW (VerizonWireless) iPhoneXS MAX, which I purchased in LateSpring2019 came EquippedWith Apple's iOS12, & updated it to the Last iOS12, which was iOS12.4.1. & IN November 2020, I was Fortunate to Receive a NEW iPhone11PRO, which came EquippedWith iOS13, so I Left that iPhone's Update automatically Because it was "buggy" & use it primarily on WiFi or MobileHotSpot & My iPhoneXS MAX as MyPrimary iOSDevice because the iOS software is More Stable For me & some of the MobileApps aren't workin' on iOS13, Like MoneyReader. Yes, I know there are "substitutes" Like EyeNote & CashReader & Microsoft's SeeingAI to Fill the Void. (Note: CashReader isn't FREE Like MoneyReader was). Hope, Iwas Able to Clear ThingsUp for ya, if not, Feel free to Ask More Questions, & I will Do MyBest to try & Fill in the Blanks: To Clear ThingsUp for ya Blessin's At 08:59 PM 8/29/2020, you wrote: I was talking about my iPhone that they wouldn't help me with a good while back unless I updated.I don't know what kind of device you're talking about, as I am not familiar with it but glad you got an answer from them. The iPhone update is not bad. Sent from my iPhone > On Aug 29, 2020, at 8:58 PM, Robin wrote: > > Okay, Ms. Shirley > After I received Your MessagePosting, which AppearsBelow this MessagePosting of Mine, I decided to Call Apple's AppleAccessibility TelephoneSupport @ 877-204-3930, To InQuire about "what" you said, & I was informed that I wouldn't Be Denied TelephoneSupport from Apple's AppleAccessibility because I refused to update My VZW XS MAX from iOS12.4.1 to WhatEver is the Latest iOS13 iteration. > > (I Presume) > it's because I didn't Update Past iOS12, as if I did "they" could say that the BugFixes were Resolved in a Future iOS update of iOS13, but since I refused to UpdatePast iOS12.4.1, I can't Be Denied TelephoneSupport from AppleAccessibility on My VZW XS MAX > At 06:30 PM 8/29/2020, you wrote: >> I just hope the device you don't have it on, you won't need help from Apple Accessibility because they told me they require you to have whatever device you're requesting help with, to be updated to the latest version or they won't help you so every since they told me that, I make sure my devices are all updated. >> >> Sent from my iPhone >> >> > On Aug 29, 2020, at 4:52 PM, Robin wrote: >> > >> > You Ask? How will "I Know"? >> > If Ya ReadMyReplyMessagePosting to ThisThread, I said, that I have Apple's iOS13 on My VZW 11PRO PrimarilyBecause that is the iOS version that it was LaunchedWith, but My VZW XS MAX wasn't, & Because of TheBugs AssociatedWith iOS13, I Refuse to Update it to iOS13, so it Remains on its Last Update, which is iOS12.4.1. >> > MayBe just MayBe >> > You're More TechSavy than I am. Yeah, that's MostLikely TheCase, as I'm not that TechSavy >> > >> > MyApologies, if this MessagePosting offends, as it isn't intended ToDoSo. >> > I'm just Stating-the-Facts, as "I See" them >> > >> > Blessin's to Those on ThisThread >> > At 01:56 PM 8/29/2020, you wrote: >> >> It's not that bad. How would you know how bad it is since you haven't updated? Some people are just unnecessarily paranoid.It's not that bad. >> >> >> >> Sent from my iPhone >> >> >> >> > On Aug 29, 2020, at 3:31 PM, Robin wrote: >> >> > >> >> > Well, TheBigDeal is iOS13 IS Buggy, which is "Why" I Refuse to Update My VZW XS MAX, as it's going to Stay ON iOS12.4.1, which is the iOS version it was when I Purchased it, & I am PrivyTo TheBugs AssociatedWith iOS13 because "They" are present on My VZW 11PRO, & that MobileDevice is ON AutomaticUpdates (so far). It's TheUser'sChoice To Update or Not >> >> > At 01:13 PM 8/29/2020, you wrote: >> >> >> You can turn automatic update off but I don't see what the big deal is with not updating. >> >> >> >> >> >> Sent from my iPhone >> >> >> >> >> >> > On Aug 29, 2020, at 7:45 AM, Joshua Hendrickson wrote: >> >> >> > >> >> >> > ï»Ã šÃ‚¿Well, the good news is, I don't really mind the new update like I >> >> >> > thought I would. The only reason why I updated, was it seemed like >> >> >> > apple did the update, and I had to enter in my touch ID. I didn't >> >> >> > have the option of saying later. There is this weird tapping thing >> >> >> > that might happen when you update. You will feel it when you swipe on >> >> >> > the screen. Just call apple accessibility and they will help you get >> >> >> > rid of that. You won't be able to check the status bar to see the >> >> >> > battery level of a bluetooth device. You have to go to battery on >> >> >> > page one of your phone to see that. Although, usually I can just ask >> >> >> > Siri current battery level and she will tell me the battery level of >> >> >> > my iPhone and a bluetooth device. If you h
Re: for Joshua
I was talking about my iPhone that they wouldn't help me with a good while back unless I updated.I don't know what kind of device you're talking about, as I am not familiar with it but glad you got an answer from them. The iPhone update is not bad. Sent from my iPhone > On Aug 29, 2020, at 8:58 PM, Robin wrote: > > Okay, Ms. Shirley > After I received Your MessagePosting, which AppearsBelow this > MessagePosting of Mine, I decided to Call Apple's AppleAccessibility > TelephoneSupport @ 877-204-3930, To InQuire about "what" you said, & I was > informed that I wouldn't Be Denied TelephoneSupport from Apple's > AppleAccessibility because I refused to update My VZW XS MAX from > iOS12.4.1 to WhatEver is the Latest iOS13 iteration. > > (I Presume) > it's because I didn't Update Past iOS12, as if I did "they" could say > that the BugFixes were Resolved in a Future iOS update of iOS13, but since I > refused to UpdatePast iOS12.4.1, I can't Be Denied TelephoneSupport from > AppleAccessibility on My VZW XS MAX > At 06:30 PM 8/29/2020, you wrote: >> I just hope the device you don't have it on, you won't need help from Apple >> Accessibility because they told me they require you to have whatever device >> you're requesting help with, to be updated to the latest version or they >> won't help you so every since they told me that, I make sure my devices are >> all updated. >> >> Sent from my iPhone >> >> > On Aug 29, 2020, at 4:52 PM, Robin wrote: >> > >> > You Ask? How will "I Know"? >> > If Ya ReadMyReplyMessagePosting to ThisThread, I said, that I have >> > Apple's iOS13 on My VZW 11PRO PrimarilyBecause that is the iOS version >> > that it was LaunchedWith, but My VZW XS MAX wasn't, & Because of TheBugs >> > AssociatedWith iOS13, I Refuse to Update it to iOS13, so it Remains on >> > its Last Update, which is iOS12.4.1. >> > MayBe just MayBe >> > You're More TechSavy than I am. Yeah, that's MostLikely TheCase, as I'm >> > not that TechSavy >> > >> > MyApologies, if this MessagePosting offends, as it isn't intended ToDoSo. >> > I'm just Stating-the-Facts, as "I See" them >> > >> > Blessin's to Those on ThisThread >> > At 01:56 PM 8/29/2020, you wrote: >> >> It's not that bad. How would you know how bad it is since you haven't >> >> updated? Some people are just unnecessarily paranoid.It's not that bad. >> >> >> >> Sent from my iPhone >> >> >> >> > On Aug 29, 2020, at 3:31 PM, Robin wrote: >> >> > >> >> > Well, TheBigDeal is iOS13 IS Buggy, which is "Why" I Refuse to >> >> > Update My VZW XS MAX, as it's going to Stay ON iOS12.4.1, which is the >> >> > iOS version it was when I Purchased it, & I am PrivyTo TheBugs >> >> > AssociatedWith iOS13 because "They" are present on My VZW 11PRO, & that >> >> > MobileDevice is ON AutomaticUpdates (so far). It's TheUser'sChoice To >> >> > Update or Not >> >> > At 01:13 PM 8/29/2020, you wrote: >> >> >> You can turn automatic update off but I don't see what the big deal is >> >> >> with not updating. >> >> >> >> >> >> Sent from my iPhone >> >> >> >> >> >> > On Aug 29, 2020, at 7:45 AM, Joshua Hendrickson >> >> >> > wrote: >> >> >> > >> >> >> > Well, the good news is, I don't really mind the new >> >> >> > update like I >> >> >> > thought I would. The only reason why I updated, was it seemed like >> >> >> > apple did the update, and I had to enter in my touch ID. I didn't >> >> >> > have the option of saying later. There is this weird tapping thing >> >> >> > that might happen when you update. You will feel it when you swipe >> >> >> > on >> >> >> > the screen. Just call apple accessibility and they will help you get >> >> >> > rid of that. You won't be able to check the status bar to see the >> >> >> > battery level of a bluetooth device. You have to go to battery on >> >> >> > page one of your phone to see that. Although, usually I can just ask >> >> >> > Siri current battery level and she will tell me the battery level of >> >> >> > my iPhone and a bluetooth device. If you have to update, good luck. >> >> >> > It really isn't that bad. >> >> >> > >> >> >> >> On 8/29/20, Judy Pryor wrote: >> >> >> >> Hi Joshua, i thought of you last night when Apple seemed to be >> >> >> >> forcing me to >> >> >> >> update . I am still on 12.4.1. It was only when I disagreed with >> >> >> >> the terms >> >> >> >> did it go away. Today they are trying again. What I wanted to know >> >> >> >> is how >> >> >> >> are you getting along with the latest update. I am using the old >> >> >> >> SE. >> >> >> >> >> >> >> >> Many thanks >> >> >> >> >> >> >> >> Judy >> >> >> >> >> >> >> >> Sent from my iPhone >> >> >> >> >> >> >> On 28 Aug 2020, at 23:16, Joshua Hendrickson >> >> >> wrote: >> >> >> >>> >> >> >> >>> Alan is correct. I also have the exchange this title option if I >> >> >> >>> enter on the menu of an audible book. However, I always have to >> >> >> >>> call >>
Re: for Joshua
I wouldn't have updated either except my iPhone kind of updated anyway even though I had automatic updates turned off. On 8/29/20, Simon A Fogarty wrote: > Sorry but which update are you speaking of? > > > -Original Message- > From: viphone@googlegroups.com On Behalf Of Diane > Giannetti > Sent: Sunday, 30 August 2020 4:19 AM > To: viphone@googlegroups.com > Subject: Re: for Joshua > > I shouldn’t think it would slow it down. As a matter of fact, as long as > your little SE will update, it should make it better. > > Sent from Diane's awesome iPhone! > >> On Aug 29, 2020, at 11:52 AM, Judy Pryor wrote: >> >> Thank you so much Joshua and Diane, perhaps i will take the plunge and >> update. Will it slow my little old SE down for a bit for a while. >> >> >> Judy >> >> Sent from my iPhone >> >>> On 29 Aug 2020, at 13:56, Diane Giannetti wrote: >>> >>> It really is a good idea to keep your phones updated. One of the main >>> reasons is Security. Another one is each time the update happens, there >>> may be some bugs, but, it’s not that bad at the phone cannot be operated >>> at all. >>> >>> Sent from Diane's awesome iPhone! >>> >>>>> On Aug 29, 2020, at 8:45 AM, Joshua Hendrickson >>>>> wrote: >>>> >>>> Well, the good news is, I don't really mind the new update like I >>>> thought I would. The only reason why I updated, was it seemed like >>>> apple did the update, and I had to enter in my touch ID. I didn't >>>> have the option of saying later. There is this weird tapping thing >>>> that might happen when you update. You will feel it when you swipe >>>> on the screen. Just call apple accessibility and they will help you >>>> get rid of that. You won't be able to check the status bar to see >>>> the battery level of a bluetooth device. You have to go to battery >>>> on page one of your phone to see that. Although, usually I can just >>>> ask Siri current battery level and she will tell me the battery >>>> level of my iPhone and a bluetooth device. If you have to update, good >>>> luck. >>>> It really isn't that bad. >>>> >>>>> On 8/29/20, Judy Pryor wrote: >>>>> Hi Joshua, i thought of you last night when Apple seemed to be >>>>> forcing me to update . I am still on 12.4.1. It was only when I >>>>> disagreed with the terms did it go away. Today they are trying >>>>> again. What I wanted to know is how are you getting along with the >>>>> latest update. I am using the old SE. >>>>> >>>>> Many thanks >>>>> >>>>> Judy >>>>> >>>>> Sent from my iPhone >>>>> >>>>>>> On 28 Aug 2020, at 23:16, Joshua Hendrickson >>>>>>> wrote: >>>>>> >>>>>> Alan is correct. I also have the exchange this title option if I >>>>>> enter on the menu of an audible book. However, I always have to >>>>>> call anyway if I want to exchange a title because I just can't >>>>>> return a book not even from the audible website. It has never >>>>>> worked for me except to phone. The option to phone audible is >>>>>> even in the app when I'm told I can't return a book. But the >>>>>> initial exchange this title is deffinately in my audible app. >>>>>> >>>>>>> On 8/28/20, Mary Otten wrote: >>>>>>> Well, Michael, I am in the states, and I don’t have that option. >>>>>>> I have all of the other options, including send this book and add >>>>>>> to favorites, but exchange is definitely not there. Multiple >>>>>>> books on more than one phone show zip. Maybe it’s because I get >>>>>>> all my credits at once? Seems very odd. >>>>>>> >>>>>>> >>>>>>> Sent from my iPhone >>>>>>> >>>>>>>> On Aug 28, 2020, at 2:55 PM, Michael Feir >>>>>>>> >>>>>>>> wrote: >>>>>>>> >>>>>>>> >>>>>>>> I think a couple of those options, "sendd this book" and >>>>>>>> "exchange this title" ar
RE: for Joshua
Sorry but which update are you speaking of? -Original Message- From: viphone@googlegroups.com On Behalf Of Diane Giannetti Sent: Sunday, 30 August 2020 4:19 AM To: viphone@googlegroups.com Subject: Re: for Joshua I shouldn’t think it would slow it down. As a matter of fact, as long as your little SE will update, it should make it better. Sent from Diane's awesome iPhone! > On Aug 29, 2020, at 11:52 AM, Judy Pryor wrote: > > Thank you so much Joshua and Diane, perhaps i will take the plunge and > update. Will it slow my little old SE down for a bit for a while. > > > Judy > > Sent from my iPhone > >> On 29 Aug 2020, at 13:56, Diane Giannetti wrote: >> >> It really is a good idea to keep your phones updated. One of the main >> reasons is Security. Another one is each time the update happens, there may >> be some bugs, but, it’s not that bad at the phone cannot be operated at all. >> >> Sent from Diane's awesome iPhone! >> >>>> On Aug 29, 2020, at 8:45 AM, Joshua Hendrickson wrote: >>> >>> Well, the good news is, I don't really mind the new update like I >>> thought I would. The only reason why I updated, was it seemed like >>> apple did the update, and I had to enter in my touch ID. I didn't >>> have the option of saying later. There is this weird tapping thing >>> that might happen when you update. You will feel it when you swipe >>> on the screen. Just call apple accessibility and they will help you >>> get rid of that. You won't be able to check the status bar to see >>> the battery level of a bluetooth device. You have to go to battery >>> on page one of your phone to see that. Although, usually I can just >>> ask Siri current battery level and she will tell me the battery >>> level of my iPhone and a bluetooth device. If you have to update, good >>> luck. >>> It really isn't that bad. >>> >>>> On 8/29/20, Judy Pryor wrote: >>>> Hi Joshua, i thought of you last night when Apple seemed to be >>>> forcing me to update . I am still on 12.4.1. It was only when I >>>> disagreed with the terms did it go away. Today they are trying >>>> again. What I wanted to know is how are you getting along with the latest >>>> update. I am using the old SE. >>>> >>>> Many thanks >>>> >>>> Judy >>>> >>>> Sent from my iPhone >>>> >>>>>> On 28 Aug 2020, at 23:16, Joshua Hendrickson wrote: >>>>> >>>>> Alan is correct. I also have the exchange this title option if I >>>>> enter on the menu of an audible book. However, I always have to >>>>> call anyway if I want to exchange a title because I just can't >>>>> return a book not even from the audible website. It has never >>>>> worked for me except to phone. The option to phone audible is >>>>> even in the app when I'm told I can't return a book. But the >>>>> initial exchange this title is deffinately in my audible app. >>>>> >>>>>> On 8/28/20, Mary Otten wrote: >>>>>> Well, Michael, I am in the states, and I don’t have that option. >>>>>> I have all of the other options, including send this book and add >>>>>> to favorites, but exchange is definitely not there. Multiple >>>>>> books on more than one phone show zip. Maybe it’s because I get >>>>>> all my credits at once? Seems very odd. >>>>>> >>>>>> >>>>>> Sent from my iPhone >>>>>> >>>>>>> On Aug 28, 2020, at 2:55 PM, Michael Feir >>>>>>> >>>>>>> wrote: >>>>>>> >>>>>>> >>>>>>> I think a couple of those options, "sendd this book" and >>>>>>> "exchange this title" are only available in the US currently. >>>>>>> I'm Canadian and need to either call Audible or go to the full >>>>>>> desktop version of the Auydible site and into "purchase history" >>>>>>> in order to return titles. A dialogue opens up over the page >>>>>>> once you double tap on "return" and then you need to navigate >>>>>>> that dialogue. Not too hard at all. I like the thought of being >>>>>>> able to re
Re: for Joshua
Okay, Ms. Shirley After I received Your MessagePosting, which AppearsBelow this MessagePosting of Mine, I decided to Call Apple's AppleAccessibility TelephoneSupport @ 877-204-3930, To InQuire about "what" you said, & I was informed that I wouldn't Be Denied TelephoneSupport from Apple's AppleAccessibility because I refused to update My VZW XS MAX from iOS12.4.1 to WhatEver is the Latest iOS13 iteration. (I Presume) it's because I didn't Update Past iOS12, as if I did "they" could say that the BugFixes were Resolved in a Future iOS update of iOS13, but since I refused to UpdatePast iOS12.4.1, I can't Be Denied TelephoneSupport from AppleAccessibility on My VZW XS MAX At 06:30 PM 8/29/2020, you wrote: I just hope the device you don't have it on, you won't need help from Apple Accessibility because they told me they require you to have whatever device you're requesting help with, to be updated to the latest version or they won't help you so every since they told me that, I make sure my devices are all updated. Sent from my iPhone > On Aug 29, 2020, at 4:52 PM, Robin wrote: > > You Ask? How will "I Know"? > If Ya ReadMyReplyMessagePosting to ThisThread, I said, that I have Apple's iOS13 on My VZW 11PRO PrimarilyBecause that is the iOS version that it was LaunchedWith, but My VZW XS MAX wasn't, & Because of TheBugs AssociatedWith iOS13, I Refuse to Update it to iOS13, so it Remains on its Last Update, which is iOS12.4.1. > MayBe just MayBe > You're More TechSavy than I am. Yeah, that's MostLikely TheCase, as I'm not that TechSavy > > MyApologies, if this MessagePosting offends, as it isn't intended ToDoSo. > I'm just Stating-the-Facts, as "I See" them > > Blessin's to Those on ThisThread > At 01:56 PM 8/29/2020, you wrote: >> It's not that bad. How would you know how bad it is since you haven't updated? Some people are just unnecessarily paranoid.It's not that bad. >> >> Sent from my iPhone >> >> > On Aug 29, 2020, at 3:31 PM, Robin wrote: >> > >> > Well, TheBigDeal is iOS13 IS Buggy, which is "Why" I Refuse to Update My VZW XS MAX, as it's going to Stay ON iOS12.4.1, which is the iOS version it was when I Purchased it, & I am PrivyTo TheBugs AssociatedWith iOS13 because "They" are present on My VZW 11PRO, & that MobileDevice is ON AutomaticUpdates (so far). It's TheUser'sChoice To Update or Not >> > At 01:13 PM 8/29/2020, you wrote: >> >> You can turn automatic update off but I don't see what the big deal is with not updating. >> >> >> >> Sent from my iPhone >> >> >> >> > On Aug 29, 2020, at 7:45 AM, Joshua Hendrickson wrote: >> >> > >> >> > Well, the good news is, I don't really mind the new update like I >> >> > thought I would. The only reason why I updated, was it seemed like >> >> > apple did the update, and I had to enter in my touch ID. I didn't >> >> > have the option of saying later. There is this weird tapping thing >> >> > that might happen when you update. You will feel it when you swipe on >> >> > the screen. Just call apple accessibility and they will help you get >> >> > rid of that. You won't be able to check the status bar to see the >> >> > battery level of a bluetooth device. You have to go to battery on >> >> > page one of your phone to see that. Although, usually I can just ask >> >> > Siri current battery level and she will tell me the battery level of >> >> > my iPhone and a bluetooth device. If you have to update, good luck. >> >> > It really isn't that bad. >> >> > >> >> >> On 8/29/20, Judy Pryor wrote: >> >> >> Hi Joshua, i thought of you last night when Apple seemed to be forcing me to >> >> >> update . I am still on 12.4.1. It was only when I disagreed with the terms >> >> >> did it go away. Today they are trying again. What I wanted to know is how >> >> >> are you getting along with the latest update. I am using the old SE. >> >> >> >> >> >> Many thanks >> >> >> >> >> >> Judy >> >> >> >> >> >> Sent from my iPhone >> >> >> >> >> On 28 Aug 2020, at 23:16, Joshua Hendrickson wrote: >> >> >>> >> >> >>> Alan is correct. I also have the exchange this title option if I >> >> >>> enter on the menu of an audible book. However, I always have to call >> >> >>> anyway if I want to exchange a title because I just can't return a >> >> >>> book not even from the audible website. It has never worked for me >> >> >>> except to phone. The option to phone audible is even in the app when >> >> >>> I'm told I can't return a book. But the initial exchange this title >> >> >>> is deffinately in my audible app. >> >> >>> >> >> On 8/28/20, Mary Otten wrote: >> >> Well, Michael, I am in the states, and I don̢ۉ„„¢t have that option. I have e >> >> all >> >> of the other options, including send this book and add to favorites, but >> >> exchange is definitely not there. Multiple books on more than one phone >> >> >>>
Re: for Joshua
I hope you don't. I was surprised when I did so should I ever need help with anything from them, I make sure it is updated. I've only encountered that one time though but don't want to give them a chance to refuse help. I updated right on the spot when they told me that. Sent from my iPhone > On Aug 29, 2020, at 8:36 PM, Robin wrote: > > Thanks for the HeadsUp, I haven't Encountered that as of Yet with Apple's > AppleAccessibility TelephoneSupport. > At 06:30 PM 8/29/2020, you wrote: >> I just hope the device you don't have it on, you won't need help from Apple >> Accessibility because they told me they require you to have whatever device >> you're requesting help with, to be updated to the latest version or they >> won't help you so every since they told me that, I make sure my devices are >> all updated. >> >> Sent from my iPhone >> >> > On Aug 29, 2020, at 4:52 PM, Robin wrote: >> > >> > You Ask? How will "I Know"? >> > If Ya ReadMyReplyMessagePosting to ThisThread, I said, that I have >> > Apple's iOS13 on My VZW 11PRO PrimarilyBecause that is the iOS version >> > that it was LaunchedWith, but My VZW XS MAX wasn't, & Because of TheBugs >> > AssociatedWith iOS13, I Refuse to Update it to iOS13, so it Remains on >> > its Last Update, which is iOS12.4.1. >> > MayBe just MayBe >> > You're More TechSavy than I am. Yeah, that's MostLikely TheCase, as I'm >> > not that TechSavy >> > >> > MyApologies, if this MessagePosting offends, as it isn't intended ToDoSo. >> > I'm just Stating-the-Facts, as "I See" them >> > >> > Blessin's to Those on ThisThread >> > At 01:56 PM 8/29/2020, you wrote: >> >> It's not that bad. How would you know how bad it is since you haven't >> >> updated? Some people are just unnecessarily paranoid.It's not that bad. >> >> >> >> Sent from my iPhone >> >> >> >> > On Aug 29, 2020, at 3:31 PM, Robin wrote: >> >> > >> >> > Well, TheBigDeal is iOS13 IS Buggy, which is "Why" I Refuse to >> >> > Update My VZW XS MAX, as it's going to Stay ON iOS12.4.1, which is the >> >> > iOS version it was when I Purchased it, & I am PrivyTo TheBugs >> >> > AssociatedWith iOS13 because "They" are present on My VZW 11PRO, & that >> >> > MobileDevice is ON AutomaticUpdates (so far). It's TheUser'sChoice To >> >> > Update or Not >> >> > At 01:13 PM 8/29/2020, you wrote: >> >> >> You can turn automatic update off but I don't see what the big deal is >> >> >> with not updating. >> >> >> >> >> >> Sent from my iPhone >> >> >> >> >> >> > On Aug 29, 2020, at 7:45 AM, Joshua Hendrickson >> >> >> > wrote: >> >> >> > >> >> >> > Well, the good news is, I don't really mind the new >> >> >> > update like I >> >> >> > thought I would. The only reason why I updated, was it seemed like >> >> >> > apple did the update, and I had to enter in my touch ID. I didn't >> >> >> > have the option of saying later. There is this weird tapping thing >> >> >> > that might happen when you update. You will feel it when you swipe >> >> >> > on >> >> >> > the screen. Just call apple accessibility and they will help you get >> >> >> > rid of that. You won't be able to check the status bar to see the >> >> >> > battery level of a bluetooth device. You have to go to battery on >> >> >> > page one of your phone to see that. Although, usually I can just ask >> >> >> > Siri current battery level and she will tell me the battery level of >> >> >> > my iPhone and a bluetooth device. If you have to update, good luck. >> >> >> > It really isn't that bad. >> >> >> > >> >> >> >> On 8/29/20, Judy Pryor wrote: >> >> >> >> Hi Joshua, i thought of you last night when Apple seemed to be >> >> >> >> forcing me to >> >> >> >> update . I am still on 12.4.1. It was only when I disagreed with >> >> >> >> the terms >> >> >> >> did it go away. Today they are trying again. What I wanted to know >> >> >> >> is how >> >> >> >> are you getting along with the latest update. I am using the old >> >> >> >> SE. >> >> >> >> >> >> >> >> Many thanks >> >> >> >> >> >> >> >> Judy >> >> >> >> >> >> >> >> Sent from my iPhone >> >> >> >> >> >> >> On 28 Aug 2020, at 23:16, Joshua Hendrickson >> >> >> wrote: >> >> >> >>> >> >> >> >>> Alan is correct. I also have the exchange this title option if I >> >> >> >>> enter on the menu of an audible book. However, I always have to >> >> >> >>> call >> >> >> >>> anyway if I want to exchange a title because I just can't return a >> >> >> >>> book not even from the audible website. It has never worked for me >> >> >> >>> except to phone. The option to phone audible is even in the app >> >> >> >>> when >> >> >> >>> I'm told I can't return a book. But the initial exchange this >> >> >> >>> title >> >> >> >>> is deffinately in my audible app. >> >> >> >>> >> >> >> On 8/28/20, Mary Otten wrote: >> >> >> Well, Michael, I am in the states, and I don̢ۉ„„¢t have >> >> >> that option. I have >> e >> >> >> all >> >>
Re: for Joshua
Thanks for the HeadsUp, I haven't Encountered that as of Yet with Apple's AppleAccessibility TelephoneSupport. At 06:30 PM 8/29/2020, you wrote: I just hope the device you don't have it on, you won't need help from Apple Accessibility because they told me they require you to have whatever device you're requesting help with, to be updated to the latest version or they won't help you so every since they told me that, I make sure my devices are all updated. Sent from my iPhone > On Aug 29, 2020, at 4:52 PM, Robin wrote: > > You Ask? How will "I Know"? > If Ya ReadMyReplyMessagePosting to ThisThread, I said, that I have Apple's iOS13 on My VZW 11PRO PrimarilyBecause that is the iOS version that it was LaunchedWith, but My VZW XS MAX wasn't, & Because of TheBugs AssociatedWith iOS13, I Refuse to Update it to iOS13, so it Remains on its Last Update, which is iOS12.4.1. > MayBe just MayBe > You're More TechSavy than I am. Yeah, that's MostLikely TheCase, as I'm not that TechSavy > > MyApologies, if this MessagePosting offends, as it isn't intended ToDoSo. > I'm just Stating-the-Facts, as "I See" them > > Blessin's to Those on ThisThread > At 01:56 PM 8/29/2020, you wrote: >> It's not that bad. How would you know how bad it is since you haven't updated? Some people are just unnecessarily paranoid.It's not that bad. >> >> Sent from my iPhone >> >> > On Aug 29, 2020, at 3:31 PM, Robin wrote: >> > >> > Well, TheBigDeal is iOS13 IS Buggy, which is "Why" I Refuse to Update My VZW XS MAX, as it's going to Stay ON iOS12.4.1, which is the iOS version it was when I Purchased it, & I am PrivyTo TheBugs AssociatedWith iOS13 because "They" are present on My VZW 11PRO, & that MobileDevice is ON AutomaticUpdates (so far). It's TheUser'sChoice To Update or Not >> > At 01:13 PM 8/29/2020, you wrote: >> >> You can turn automatic update off but I don't see what the big deal is with not updating. >> >> >> >> Sent from my iPhone >> >> >> >> > On Aug 29, 2020, at 7:45 AM, Joshua Hendrickson wrote: >> >> > >> >> > Well, the good news is, I don't really mind the new update like I >> >> > thought I would. The only reason why I updated, was it seemed like >> >> > apple did the update, and I had to enter in my touch ID. I didn't >> >> > have the option of saying later. There is this weird tapping thing >> >> > that might happen when you update. You will feel it when you swipe on >> >> > the screen. Just call apple accessibility and they will help you get >> >> > rid of that. You won't be able to check the status bar to see the >> >> > battery level of a bluetooth device. You have to go to battery on >> >> > page one of your phone to see that. Although, usually I can just ask >> >> > Siri current battery level and she will tell me the battery level of >> >> > my iPhone and a bluetooth device. If you have to update, good luck. >> >> > It really isn't that bad. >> >> > >> >> >> On 8/29/20, Judy Pryor wrote: >> >> >> Hi Joshua, i thought of you last night when Apple seemed to be forcing me to >> >> >> update . I am still on 12.4.1. It was only when I disagreed with the terms >> >> >> did it go away. Today they are trying again. What I wanted to know is how >> >> >> are you getting along with the latest update. I am using the old SE. >> >> >> >> >> >> Many thanks >> >> >> >> >> >> Judy >> >> >> >> >> >> Sent from my iPhone >> >> >> >> >> On 28 Aug 2020, at 23:16, Joshua Hendrickson wrote: >> >> >>> >> >> >>> Alan is correct. I also have the exchange this title option if I >> >> >>> enter on the menu of an audible book. However, I always have to call >> >> >>> anyway if I want to exchange a title because I just can't return a >> >> >>> book not even from the audible website. It has never worked for me >> >> >>> except to phone. The option to phone audible is even in the app when >> >> >>> I'm told I can't return a book. But the initial exchange this title >> >> >>> is deffinately in my audible app. >> >> >>> >> >> On 8/28/20, Mary Otten wrote: >> >> Well, Michael, I am in the states, and I don̢ۉ„„¢t have that option. I have e >> >> all >> >> of the other options, including send this book and add to favorites, but >> >> exchange is definitely not there. Multiple books on more than one phone >> >> show >> >> zip. Maybe it’s because I get all ml my creditsits at once? Seems very odd. >> >> >> >> >> >> Sent from my iPhone >> >> >> >> > On Aug 28, 2020, at 2:55 PM, Michael Feir >> >> > wrote: >> >> > >> >> >  >> >> > I think a couple of those options, "sendd this book" and "exchange this >> >> > title" are only available in the US currently. I'm Canadian and need to >> >> > either call Audible or go to the full desktop version of the Auydible >> >> > site >> >> > and into "purchase history" in order to r
Re: for Joshua
I just hope the device you don't have it on, you won't need help from Apple Accessibility because they told me they require you to have whatever device you're requesting help with, to be updated to the latest version or they won't help you so every since they told me that, I make sure my devices are all updated. Sent from my iPhone > On Aug 29, 2020, at 4:52 PM, Robin wrote: > > You Ask? How will "I Know"? > If Ya ReadMyReplyMessagePosting to ThisThread, I said, that I have Apple's > iOS13 on My VZW 11PRO PrimarilyBecause that is the iOS version that it was > LaunchedWith, but My VZW XS MAX wasn't, & Because of TheBugs AssociatedWith > iOS13, I Refuse to Update it to iOS13, so it Remains on its Last Update, > which is iOS12.4.1. > MayBe just MayBe > You're More TechSavy than I am. Yeah, that's MostLikely TheCase, as I'm not > that TechSavy > > MyApologies, if this MessagePosting offends, as it isn't intended ToDoSo. > I'm just Stating-the-Facts, as "I See" them > > Blessin's to Those on ThisThread > At 01:56 PM 8/29/2020, you wrote: >> It's not that bad. How would you know how bad it is since you haven't >> updated? Some people are just unnecessarily paranoid.It's not that bad. >> >> Sent from my iPhone >> >> > On Aug 29, 2020, at 3:31 PM, Robin wrote: >> > >> > Well, TheBigDeal is iOS13 IS Buggy, which is "Why" I Refuse to Update >> > My VZW XS MAX, as it's going to Stay ON iOS12.4.1, which is the iOS >> > version it was when I Purchased it, & I am PrivyTo TheBugs >> > AssociatedWith iOS13 because "They" are present on My VZW 11PRO, & that >> > MobileDevice is ON AutomaticUpdates (so far). It's TheUser'sChoice To >> > Update or Not >> > At 01:13 PM 8/29/2020, you wrote: >> >> You can turn automatic update off but I don't see what the big deal is >> >> with not updating. >> >> >> >> Sent from my iPhone >> >> >> >> > On Aug 29, 2020, at 7:45 AM, Joshua Hendrickson >> >> > wrote: >> >> > >> >> > Well, the good news is, I don't really mind the new update like I >> >> > thought I would. The only reason why I updated, was it seemed like >> >> > apple did the update, and I had to enter in my touch ID. I didn't >> >> > have the option of saying later. There is this weird tapping thing >> >> > that might happen when you update. You will feel it when you swipe on >> >> > the screen. Just call apple accessibility and they will help you get >> >> > rid of that. You won't be able to check the status bar to see the >> >> > battery level of a bluetooth device. You have to go to battery on >> >> > page one of your phone to see that. Although, usually I can just ask >> >> > Siri current battery level and she will tell me the battery level of >> >> > my iPhone and a bluetooth device. If you have to update, good luck. >> >> > It really isn't that bad. >> >> > >> >> >> On 8/29/20, Judy Pryor wrote: >> >> >> Hi Joshua, i thought of you last night when Apple seemed to be forcing >> >> >> me to >> >> >> update . I am still on 12.4.1. It was only when I disagreed with the >> >> >> terms >> >> >> did it go away. Today they are trying again. What I wanted to know is >> >> >> how >> >> >> are you getting along with the latest update. I am using the old SE. >> >> >> >> >> >> Many thanks >> >> >> >> >> >> Judy >> >> >> >> >> >> Sent from my iPhone >> >> >> >> >> On 28 Aug 2020, at 23:16, Joshua Hendrickson >> >> wrote: >> >> >>> >> >> >>> Alan is correct. I also have the exchange this title option if I >> >> >>> enter on the menu of an audible book. However, I always have to call >> >> >>> anyway if I want to exchange a title because I just can't return a >> >> >>> book not even from the audible website. It has never worked for me >> >> >>> except to phone. The option to phone audible is even in the app when >> >> >>> I'm told I can't return a book. But the initial exchange this title >> >> >>> is deffinately in my audible app. >> >> >>> >> >> On 8/28/20, Mary Otten wrote: >> >> Well, Michael, I am in the states, and I donâ€â„„¢t have that >> >> option. I have >> >> all >> >> of the other options, including send this book and add to favorites, >> >> but >> >> exchange is definitely not there. Multiple books on more than one >> >> phone >> >> show >> >> zip. Maybe it’s because I get all my creditsits at once? Seems >> >> very odd. >> >> >> >> >> >> Sent from my iPhone >> >> >> >> > On Aug 28, 2020, at 2:55 PM, Michael Feir >> >> > wrote: >> >> > >> >> >  >> >> > I think a couple of those options, "sendd this book" and "exchange >> >> > this >> >> > title" are only available in the US currently. I'm Canadian and >> >> > need to >> >> > either call Audible or go to the full desktop version of the >> >> > Auydible >> >> > site >> >> > and into "purchase history" in order to return titles. A dialogue >> >> >>>
Re: for Joshua
You Ask? How will "I Know"? If Ya ReadMyReplyMessagePosting to ThisThread, I said, that I have Apple's iOS13 on My VZW 11PRO PrimarilyBecause that is the iOS version that it was LaunchedWith, but My VZW XS MAX wasn't, & Because of TheBugs AssociatedWith iOS13, I Refuse to Update it to iOS13, so it Remains on its Last Update, which is iOS12.4.1. MayBe just MayBe You're More TechSavy than I am. Yeah, that's MostLikely TheCase, as I'm not that TechSavy MyApologies, if this MessagePosting offends, as it isn't intended ToDoSo. I'm just Stating-the-Facts, as "I See" them Blessin's to Those on ThisThread At 01:56 PM 8/29/2020, you wrote: It's not that bad. How would you know how bad it is since you haven't updated? Some people are just unnecessarily paranoid.It's not that bad. Sent from my iPhone > On Aug 29, 2020, at 3:31 PM, Robin wrote: > > Well, TheBigDeal is iOS13 IS Buggy, which is "Why" I Refuse to Update My VZW XS MAX, as it's going to Stay ON iOS12.4.1, which is the iOS version it was when I Purchased it, & I am PrivyTo TheBugs AssociatedWith iOS13 because "They" are present on My VZW 11PRO, & that MobileDevice is ON AutomaticUpdates (so far). It's TheUser'sChoice To Update or Not > At 01:13 PM 8/29/2020, you wrote: >> You can turn automatic update off but I don't see what the big deal is with not updating. >> >> Sent from my iPhone >> >> > On Aug 29, 2020, at 7:45 AM, Joshua Hendrickson wrote: >> > >> > Well, the good news is, I don't really mind the new update like I >> > thought I would. The only reason why I updated, was it seemed like >> > apple did the update, and I had to enter in my touch ID. I didn't >> > have the option of saying later. There is this weird tapping thing >> > that might happen when you update. You will feel it when you swipe on >> > the screen. Just call apple accessibility and they will help you get >> > rid of that. You won't be able to check the status bar to see the >> > battery level of a bluetooth device. You have to go to battery on >> > page one of your phone to see that. Although, usually I can just ask >> > Siri current battery level and she will tell me the battery level of >> > my iPhone and a bluetooth device. If you have to update, good luck. >> > It really isn't that bad. >> > >> >> On 8/29/20, Judy Pryor wrote: >> >> Hi Joshua, i thought of you last night when Apple seemed to be forcing me to >> >> update . I am still on 12.4.1. It was only when I disagreed with the terms >> >> did it go away. Today they are trying again. What I wanted to know is how >> >> are you getting along with the latest update. I am using the old SE. >> >> >> >> Many thanks >> >> >> >> Judy >> >> >> >> Sent from my iPhone >> >> >> On 28 Aug 2020, at 23:16, Joshua Hendrickson wrote: >> >>> >> >>> Alan is correct. I also have the exchange this title option if I >> >>> enter on the menu of an audible book. However, I always have to call >> >>> anyway if I want to exchange a title because I just can't return a >> >>> book not even from the audible website. It has never worked for me >> >>> except to phone. The option to phone audible is even in the app when >> >>> I'm told I can't return a book. But the initial exchange this title >> >>> is deffinately in my audible app. >> >>> >> On 8/28/20, Mary Otten wrote: >> Well, Michael, I am in the states, and I donâ€â„„¢t have that option. I have >> all >> of the other options, including send this book and add to favorites, but >> exchange is definitely not there. Multiple books on more than one phone >> show >> zip. Maybe it’s because I get all my creditsits at once? Seems very odd. >> >> >> Sent from my iPhone >> >> > On Aug 28, 2020, at 2:55 PM, Michael Feir >> > wrote: >> > >> >  >> > I think a couple of those options, "sendd this book" and "exchange this >> > title" are only available in the US currently. I'm Canadian and need to >> > either call Audible or go to the full desktop version of the Auydible >> > site >> > and into "purchase history" in order to return titles. A dialogue opens >> > up >> > over the page once you double tap on "return" and then you need to >> > navigate that dialogue. Not too hard at all. I like the thought of >> > being >> > able to return books from right in the app so I hope they extend that >> > option to Canada. >> > >> >> On Fri, Aug 28, 2020 at 5:42 PM Richard Turner >> >> wrote: >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> I just checked, and if you flick right once from the title of the book >> >> and double tap on the button labeled Menu, The buttons are: >> >> >> >> Book Details, >> >> >> >> >> >> Rate and Review, >> >> >> >> >> >> Mark as Finished, >> >> >>
Re: for Joshua
It's not that bad. How would you know how bad it is since you haven't updated? Some people are just unnecessarily paranoid.It's not that bad. Sent from my iPhone > On Aug 29, 2020, at 3:31 PM, Robin wrote: > > Well, TheBigDeal is iOS13 IS Buggy, which is "Why" I Refuse to Update My > VZW XS MAX, as it's going to Stay ON iOS12.4.1, which is the iOS version it > was when I Purchased it, & I am PrivyTo TheBugs AssociatedWith iOS13 > because "They" are present on My VZW 11PRO, & that MobileDevice is ON > AutomaticUpdates (so far). It's TheUser'sChoice To Update or Not > At 01:13 PM 8/29/2020, you wrote: >> You can turn automatic update off but I don't see what the big deal is with >> not updating. >> >> Sent from my iPhone >> >> > On Aug 29, 2020, at 7:45 AM, Joshua Hendrickson wrote: >> > >> > Well, the good news is, I don't really mind the new update like I >> > thought I would. The only reason why I updated, was it seemed like >> > apple did the update, and I had to enter in my touch ID. I didn't >> > have the option of saying later. There is this weird tapping thing >> > that might happen when you update. You will feel it when you swipe on >> > the screen. Just call apple accessibility and they will help you get >> > rid of that. You won't be able to check the status bar to see the >> > battery level of a bluetooth device. You have to go to battery on >> > page one of your phone to see that. Although, usually I can just ask >> > Siri current battery level and she will tell me the battery level of >> > my iPhone and a bluetooth device. If you have to update, good luck. >> > It really isn't that bad. >> > >> >> On 8/29/20, Judy Pryor wrote: >> >> Hi Joshua, i thought of you last night when Apple seemed to be forcing me >> >> to >> >> update . I am still on 12.4.1. It was only when I disagreed with the >> >> terms >> >> did it go away. Today they are trying again. What I wanted to know is how >> >> are you getting along with the latest update. I am using the old SE. >> >> >> >> Many thanks >> >> >> >> Judy >> >> >> >> Sent from my iPhone >> >> >> On 28 Aug 2020, at 23:16, Joshua Hendrickson wrote: >> >>> >> >>> Alan is correct. I also have the exchange this title option if I >> >>> enter on the menu of an audible book. However, I always have to call >> >>> anyway if I want to exchange a title because I just can't return a >> >>> book not even from the audible website. It has never worked for me >> >>> except to phone. The option to phone audible is even in the app when >> >>> I'm told I can't return a book. But the initial exchange this title >> >>> is deffinately in my audible app. >> >>> >> On 8/28/20, Mary Otten wrote: >> Well, Michael, I am in the states, and I don’t have that option. I >> have >> all >> of the other options, including send this book and add to favorites, but >> exchange is definitely not there. Multiple books on more than one phone >> show >> zip. Maybe it’s because I get all my credits at once? Seems very odd. >> >> >> Sent from my iPhone >> >> > On Aug 28, 2020, at 2:55 PM, Michael Feir >> > wrote: >> > >> >  >> > I think a couple of those options, "sendd this book" and "exchange this >> > title" are only available in the US currently. I'm Canadian and need to >> > either call Audible or go to the full desktop version of the Auydible >> > site >> > and into "purchase history" in order to return titles. A dialogue opens >> > up >> > over the page once you double tap on "return" and then you need to >> > navigate that dialogue. Not too hard at all. I like the thought of >> > being >> > able to return books from right in the app so I hope they extend that >> > option to Canada. >> > >> >> On Fri, Aug 28, 2020 at 5:42 PM Richard Turner >> >> wrote: >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> I just checked, and if you flick right once from the title of the book >> >> and double tap on the button labeled Menu, The buttons are: >> >> >> >> Book Details, >> >> >> >> >> >> Rate and Review, >> >> >> >> >> >> Mark as Finished, >> >> >> >> >> >> Exchange this title, >> >> >> >> >> >> Send This Boo, >> >> >> >> >> >> Add to favorites, >> >> >> >> >> >> Cancel. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> HTH, >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Richard >> >> >> >> >> >> "He that cannot forgive others breaks the bridge over which he must >> >> pass >> >> himself,†and we forget that only grace can break the cycle of >> >> ancient
Re: for Joshua
Well, TheBigDeal is iOS13 IS Buggy, which is "Why" I Refuse to Update My VZW XS MAX, as it's going to Stay ON iOS12.4.1, which is the iOS version it was when I Purchased it, & I am PrivyTo TheBugs AssociatedWith iOS13 because "They" are present on My VZW 11PRO, & that MobileDevice is ON AutomaticUpdates (so far). It's TheUser'sChoice To Update or Not At 01:13 PM 8/29/2020, you wrote: You can turn automatic update off but I don't see what the big deal is with not updating. Sent from my iPhone > On Aug 29, 2020, at 7:45 AM, Joshua Hendrickson wrote: > > Well, the good news is, I don't really mind the new update like I > thought I would. The only reason why I updated, was it seemed like > apple did the update, and I had to enter in my touch ID. I didn't > have the option of saying later. There is this weird tapping thing > that might happen when you update. You will feel it when you swipe on > the screen. Just call apple accessibility and they will help you get > rid of that. You won't be able to check the status bar to see the > battery level of a bluetooth device. You have to go to battery on > page one of your phone to see that. Although, usually I can just ask > Siri current battery level and she will tell me the battery level of > my iPhone and a bluetooth device. If you have to update, good luck. > It really isn't that bad. > >> On 8/29/20, Judy Pryor wrote: >> Hi Joshua, i thought of you last night when Apple seemed to be forcing me to >> update . I am still on 12.4.1. It was only when I disagreed with the terms >> did it go away. Today they are trying again. What I wanted to know is how >> are you getting along with the latest update. I am using the old SE. >> >> Many thanks >> >> Judy >> >> Sent from my iPhone >> On 28 Aug 2020, at 23:16, Joshua Hendrickson wrote: >>> >>> Alan is correct. I also have the exchange this title option if I >>> enter on the menu of an audible book. However, I always have to call >>> anyway if I want to exchange a title because I just can't return a >>> book not even from the audible website. It has never worked for me >>> except to phone. The option to phone audible is even in the app when >>> I'm told I can't return a book. But the initial exchange this title >>> is deffinately in my audible app. >>> On 8/28/20, Mary Otten wrote: Well, Michael, I am in the states, and I don’t have that option. I have all of the other options, including send this book and add to favorites, but exchange is definitely not there. Multiple books on more than one phone show zip. Maybe it’s because I get all my credits at once? Seems very odd. Sent from my iPhone > On Aug 28, 2020, at 2:55 PM, Michael Feir > wrote: > >  > I think a couple of those options, "sendd this book" and "exchange this > title" are only available in the US currently. I'm Canadian and need to > either call Audible or go to the full desktop version of the Auydible > site > and into "purchase history" in order to return titles. A dialogue opens > up > over the page once you double tap on "return" and then you need to > navigate that dialogue. Not too hard at all. I like the thought of > being > able to return books from right in the app so I hope they extend that > option to Canada. > >> On Fri, Aug 28, 2020 at 5:42 PM Richard Turner >> wrote: >> >> >> >> >> >> >> >> >> >> >> I just checked, and if you flick right once from the title of the book >> and double tap on the button labeled Menu, The buttons are: >> >> Book Details, >> >> >> Rate and Review, >> >> >> Mark as Finished, >> >> >> Exchange this title, >> >> >> Send This Boo, >> >> >> Add to favorites, >> >> >> Cancel. >> >> >> >> >> >> >> >> HTH, >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Richard >> >> >> "He that cannot forgive others breaks the bridge over which he must >> pass >> himself,†and we forget that only grace can break the cycle of ancient >> hatreds among peoples. (It is notable that while I have regretted not >> granting >> >> grace to others, I’ve never once regretted extending it.)" - Edward >> Herbert >> >> >> >> >> >> >> >> >> >>> On Aug 28, 2020, at 2:28 PM, Alan Lemly wrote: >>> >>> >>> >>> >>> >> >> >> >> >>> >>> >>> Mary, >>> >>> >>> >>> >>> >>> When I'm in my Library tab on the iOS Audible app and double tap the >>> Menu button to the right of one of my listed books, I get a list of >>> vertically stacked options one of which is Ex
Re: for Joshua
You can turn automatic update off but I don't see what the big deal is with not updating. Sent from my iPhone > On Aug 29, 2020, at 7:45 AM, Joshua Hendrickson wrote: > > Well, the good news is, I don't really mind the new update like I > thought I would. The only reason why I updated, was it seemed like > apple did the update, and I had to enter in my touch ID. I didn't > have the option of saying later. There is this weird tapping thing > that might happen when you update. You will feel it when you swipe on > the screen. Just call apple accessibility and they will help you get > rid of that. You won't be able to check the status bar to see the > battery level of a bluetooth device. You have to go to battery on > page one of your phone to see that. Although, usually I can just ask > Siri current battery level and she will tell me the battery level of > my iPhone and a bluetooth device. If you have to update, good luck. > It really isn't that bad. > >> On 8/29/20, Judy Pryor wrote: >> Hi Joshua, i thought of you last night when Apple seemed to be forcing me to >> update . I am still on 12.4.1. It was only when I disagreed with the terms >> did it go away. Today they are trying again. What I wanted to know is how >> are you getting along with the latest update. I am using the old SE. >> >> Many thanks >> >> Judy >> >> Sent from my iPhone >> On 28 Aug 2020, at 23:16, Joshua Hendrickson wrote: >>> >>> Alan is correct. I also have the exchange this title option if I >>> enter on the menu of an audible book. However, I always have to call >>> anyway if I want to exchange a title because I just can't return a >>> book not even from the audible website. It has never worked for me >>> except to phone. The option to phone audible is even in the app when >>> I'm told I can't return a book. But the initial exchange this title >>> is deffinately in my audible app. >>> On 8/28/20, Mary Otten wrote: Well, Michael, I am in the states, and I don’t have that option. I have all of the other options, including send this book and add to favorites, but exchange is definitely not there. Multiple books on more than one phone show zip. Maybe it’s because I get all my credits at once? Seems very odd. Sent from my iPhone > On Aug 28, 2020, at 2:55 PM, Michael Feir > wrote: > > > I think a couple of those options, "sendd this book" and "exchange this > title" are only available in the US currently. I'm Canadian and need to > either call Audible or go to the full desktop version of the Auydible > site > and into "purchase history" in order to return titles. A dialogue opens > up > over the page once you double tap on "return" and then you need to > navigate that dialogue. Not too hard at all. I like the thought of > being > able to return books from right in the app so I hope they extend that > option to Canada. > >> On Fri, Aug 28, 2020 at 5:42 PM Richard Turner >> wrote: >> >> >> >> >> >> >> >> >> >> >> I just checked, and if you flick right once from the title of the book >> and double tap on the button labeled Menu, The buttons are: >> >> Book Details, >> >> >> Rate and Review, >> >> >> Mark as Finished, >> >> >> Exchange this title, >> >> >> Send This Boo, >> >> >> Add to favorites, >> >> >> Cancel. >> >> >> >> >> >> >> >> HTH, >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Richard >> >> >> "He that cannot forgive others breaks the bridge over which he must >> pass >> himself,” and we forget that only grace can break the cycle of ancient >> hatreds among peoples. (It is notable that while I have regretted not >> granting >> >> grace to others, I’ve never once regretted extending it.)" - Edward >> Herbert >> >> >> >> >> >> >> >> >> >>> On Aug 28, 2020, at 2:28 PM, Alan Lemly wrote: >>> >>> >>> >>> >>> >> >> >> >> >>> >>> >>> Mary, >>> >>> >>> >>> >>> >>> When I'm in my Library tab on the iOS Audible app and double tap the >>> Menu button to the right of one of my listed books, I get a list of >>> vertically stacked options one of which is Exchange this title. >>> >>> >>> >>> >>> >>> Alan Lemly >>> >>> >>> >>> >>> >>> -Original Message- >>> >>> >>> From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On >>> Behalf Of Mary Otten >>> >>> >>> Sent: Friday, August
Re: for Joshua
Thank you Karen and Diane Judy Sent from my iPhone > On 29 Aug 2020, at 17:09, Karen Poulakos wrote: > > I am using an older SE, and it's working just fine with the update. > > Karen P > > -Original Message- > From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf Of > Judy Pryor > Sent: Saturday, August 29, 2020 10:52 AM > To: viphone@googlegroups.com > Subject: Re: for Joshua > > Thank you so much Joshua and Diane, perhaps i will take the plunge and > update. Will it slow my little old SE down for a bit for a while. > > > Judy > > Sent from my iPhone > >> On 29 Aug 2020, at 13:56, Diane Giannetti wrote: >> >> It really is a good idea to keep your phones updated. One of the main >> reasons is Security. Another one is each time the update happens, there may >> be some bugs, but, it�s not that bad at the phone cannot be operated at all. >> >> Sent from Diane's awesome iPhone! >> >>> On Aug 29, 2020, at 8:45 AM, Joshua Hendrickson wrote: >>> >>> ?Well, the good news is, I don't really mind the new update like I >>> thought I would. The only reason why I updated, was it seemed like >>> apple did the update, and I had to enter in my touch ID. I didn't >>> have the option of saying later. There is this weird tapping thing >>> that might happen when you update. You will feel it when you swipe on >>> the screen. Just call apple accessibility and they will help you get >>> rid of that. You won't be able to check the status bar to see the >>> battery level of a bluetooth device. You have to go to battery on >>> page one of your phone to see that. Although, usually I can just ask >>> Siri current battery level and she will tell me the battery level of >>> my iPhone and a bluetooth device. If you have to update, good luck. >>> It really isn't that bad. >>> >>>> On 8/29/20, Judy Pryor wrote: >>>> Hi Joshua, i thought of you last night when Apple seemed to be forcing me >>>> to >>>> update . I am still on 12.4.1. It was only when I disagreed with the >>>> terms >>>> did it go away. Today they are trying again. What I wanted to know is how >>>> are you getting along with the latest update. I am using the old SE. >>>> >>>> Many thanks >>>> >>>> Judy >>>> >>>> Sent from my iPhone >>>> >>>>>> On 28 Aug 2020, at 23:16, Joshua Hendrickson wrote: >>>>> >>>>> Alan is correct. I also have the exchange this title option if I >>>>> enter on the menu of an audible book. However, I always have to call >>>>> anyway if I want to exchange a title because I just can't return a >>>>> book not even from the audible website. It has never worked for me >>>>> except to phone. The option to phone audible is even in the app when >>>>> I'm told I can't return a book. But the initial exchange this title >>>>> is deffinately in my audible app. >>>>> >>>>>> On 8/28/20, Mary Otten wrote: >>>>>> Well, Michael, I am in the states, and I don�t have that option. I have >>>>>> all >>>>>> of the other options, including send this book and add to favorites, but >>>>>> exchange is definitely not there. Multiple books on more than one phone >>>>>> show >>>>>> zip. Maybe it�s because I get all my credits at once? Seems very odd. >>>>>> >>>>>> >>>>>> Sent from my iPhone >>>>>> >>>>>>> On Aug 28, 2020, at 2:55 PM, Michael Feir >>>>>>> wrote: >>>>>>> >>>>>>> ? >>>>>>> I think a couple of those options, "sendd this book" and "exchange this >>>>>>> title" are only available in the US currently. I'm Canadian and need to >>>>>>> either call Audible or go to the full desktop version of the Auydible >>>>>>> site >>>>>>> and into "purchase history" in order to return titles. A dialogue opens >>>>>>> up >>>>>>> over the page once you double tap on "return" and then you need to >>>>>>> navigate that dialogue. Not too hard at all. I like the thought of >>>>>>> being >>
RE: for Joshua
Joshua, That weird tapping thing you referenced after your upgrade to iOS 13.x is called haptic feedback. I was also a bit surprised by it when I first upgraded to iOS 13 but I'd suggest you leave it on and try it out for a while. I expect it is helpful to those who also have a hearing impairment. You can change the intensity level of the haptic feedback at Settings, Accessibility, Voiceover, Audio, Sounds and haptics. There is a Haptics heading on this screen and just below it is a button to turn it on or off. Just below that is a control to set the intensity level. You can single finger swipe up or down this control to change the intensity in multiple degrees or you can single finger tap and hold the control and slide left or right to change the intensity granularity with more precision. Alan Lemly -Original Message- From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf Of Joshua Hendrickson Sent: Saturday, August 29, 2020 7:45 AM To: viphone@googlegroups.com Subject: Re: for Joshua Well, the good news is, I don't really mind the new update like I thought I would. The only reason why I updated, was it seemed like apple did the update, and I had to enter in my touch ID. I didn't have the option of saying later. There is this weird tapping thing that might happen when you update. You will feel it when you swipe on the screen. Just call apple accessibility and they will help you get rid of that. You won't be able to check the status bar to see the battery level of a bluetooth device. You have to go to battery on page one of your phone to see that. Although, usually I can just ask Siri current battery level and she will tell me the battery level of my iPhone and a bluetooth device. If you have to update, good luck. It really isn't that bad. On 8/29/20, Judy Pryor wrote: > Hi Joshua, i thought of you last night when Apple seemed to be forcing > me to update . I am still on 12.4.1. It was only when I disagreed > with the terms did it go away. Today they are trying again. What I > wanted to know is how are you getting along with the latest update. I am > using the old SE. > > Many thanks > > Judy > > Sent from my iPhone > >> On 28 Aug 2020, at 23:16, Joshua Hendrickson wrote: >> >> Alan is correct. I also have the exchange this title option if I >> enter on the menu of an audible book. However, I always have to call >> anyway if I want to exchange a title because I just can't return a >> book not even from the audible website. It has never worked for me >> except to phone. The option to phone audible is even in the app when >> I'm told I can't return a book. But the initial exchange this title >> is deffinately in my audible app. >> >>> On 8/28/20, Mary Otten wrote: >>> Well, Michael, I am in the states, and I don t have that option. I >>> have all of the other options, including send this book and add to >>> favorites, but exchange is definitely not there. Multiple books on >>> more than one phone show zip. Maybe it s because I get all my >>> credits at once? Seems very odd. >>> >>> >>> Sent from my iPhone >>> >>>> On Aug 28, 2020, at 2:55 PM, Michael Feir >>>> wrote: >>>> >>>> ? >>>> I think a couple of those options, "sendd this book" and "exchange >>>> this title" are only available in the US currently. I'm Canadian >>>> and need to either call Audible or go to the full desktop version >>>> of the Auydible site and into "purchase history" in order to return >>>> titles. A dialogue opens up over the page once you double tap on >>>> "return" and then you need to navigate that dialogue. Not too hard >>>> at all. I like the thought of being able to return books from right >>>> in the app so I hope they extend that option to Canada. >>>> >>>>> On Fri, Aug 28, 2020 at 5:42 PM Richard Turner >>>>> wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> I just checked, and if you flick right once from the title of the >>>>> book and double tap on the button labeled Menu, The buttons are: >>>>> >>>>> Book Details, >>>>> >>>>> >>>>> Rate and Review, >>>>> >>>>> >>>>> Mark as Finished, >>>>> >>
Re: for Joshua
I shouldn’t think it would slow it down. As a matter of fact, as long as your little SE will update, it should make it better. Sent from Diane's awesome iPhone! > On Aug 29, 2020, at 11:52 AM, Judy Pryor wrote: > > Thank you so much Joshua and Diane, perhaps i will take the plunge and > update. Will it slow my little old SE down for a bit for a while. > > > Judy > > Sent from my iPhone > >> On 29 Aug 2020, at 13:56, Diane Giannetti wrote: >> >> It really is a good idea to keep your phones updated. One of the main >> reasons is Security. Another one is each time the update happens, there may >> be some bugs, but, it’s not that bad at the phone cannot be operated at all. >> >> Sent from Diane's awesome iPhone! >> On Aug 29, 2020, at 8:45 AM, Joshua Hendrickson wrote: >>> >>> Well, the good news is, I don't really mind the new update like I >>> thought I would. The only reason why I updated, was it seemed like >>> apple did the update, and I had to enter in my touch ID. I didn't >>> have the option of saying later. There is this weird tapping thing >>> that might happen when you update. You will feel it when you swipe on >>> the screen. Just call apple accessibility and they will help you get >>> rid of that. You won't be able to check the status bar to see the >>> battery level of a bluetooth device. You have to go to battery on >>> page one of your phone to see that. Although, usually I can just ask >>> Siri current battery level and she will tell me the battery level of >>> my iPhone and a bluetooth device. If you have to update, good luck. >>> It really isn't that bad. >>> On 8/29/20, Judy Pryor wrote: Hi Joshua, i thought of you last night when Apple seemed to be forcing me to update . I am still on 12.4.1. It was only when I disagreed with the terms did it go away. Today they are trying again. What I wanted to know is how are you getting along with the latest update. I am using the old SE. Many thanks Judy Sent from my iPhone >> On 28 Aug 2020, at 23:16, Joshua Hendrickson wrote: > > Alan is correct. I also have the exchange this title option if I > enter on the menu of an audible book. However, I always have to call > anyway if I want to exchange a title because I just can't return a > book not even from the audible website. It has never worked for me > except to phone. The option to phone audible is even in the app when > I'm told I can't return a book. But the initial exchange this title > is deffinately in my audible app. > >> On 8/28/20, Mary Otten wrote: >> Well, Michael, I am in the states, and I don’t have that option. I have >> all >> of the other options, including send this book and add to favorites, but >> exchange is definitely not there. Multiple books on more than one phone >> show >> zip. Maybe it’s because I get all my credits at once? Seems very odd. >> >> >> Sent from my iPhone >> >>> On Aug 28, 2020, at 2:55 PM, Michael Feir >>> wrote: >>> >>> >>> I think a couple of those options, "sendd this book" and "exchange this >>> title" are only available in the US currently. I'm Canadian and need to >>> either call Audible or go to the full desktop version of the Auydible >>> site >>> and into "purchase history" in order to return titles. A dialogue opens >>> up >>> over the page once you double tap on "return" and then you need to >>> navigate that dialogue. Not too hard at all. I like the thought of >>> being >>> able to return books from right in the app so I hope they extend that >>> option to Canada. >>> On Fri, Aug 28, 2020 at 5:42 PM Richard Turner wrote: I just checked, and if you flick right once from the title of the book and double tap on the button labeled Menu, The buttons are: Book Details, Rate and Review, Mark as Finished, Exchange this title, Send This Boo, Add to favorites, Cancel. HTH, Richard "He that cannot forgive others breaks the bridge over which he must pass himself,” and we forget that only grace can break the cycle of ancient hatreds among peoples. (It is notable that while I have regretted not granting >>>
RE: for Joshua
I am using an older SE, and it's working just fine with the update. Karen P -Original Message- From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf Of Judy Pryor Sent: Saturday, August 29, 2020 10:52 AM To: viphone@googlegroups.com Subject: Re: for Joshua Thank you so much Joshua and Diane, perhaps i will take the plunge and update. Will it slow my little old SE down for a bit for a while. Judy Sent from my iPhone > On 29 Aug 2020, at 13:56, Diane Giannetti wrote: > > It really is a good idea to keep your phones updated. One of the main reasons > is Security. Another one is each time the update happens, there may be some > bugs, but, it�s not that bad at the phone cannot be operated at all. > > Sent from Diane's awesome iPhone! > >> On Aug 29, 2020, at 8:45 AM, Joshua Hendrickson wrote: >> >> ?Well, the good news is, I don't really mind the new update like I >> thought I would. The only reason why I updated, was it seemed like >> apple did the update, and I had to enter in my touch ID. I didn't >> have the option of saying later. There is this weird tapping thing >> that might happen when you update. You will feel it when you swipe on >> the screen. Just call apple accessibility and they will help you get >> rid of that. You won't be able to check the status bar to see the >> battery level of a bluetooth device. You have to go to battery on >> page one of your phone to see that. Although, usually I can just ask >> Siri current battery level and she will tell me the battery level of >> my iPhone and a bluetooth device. If you have to update, good luck. >> It really isn't that bad. >> >>> On 8/29/20, Judy Pryor wrote: >>> Hi Joshua, i thought of you last night when Apple seemed to be forcing me to >>> update . I am still on 12.4.1. It was only when I disagreed with the terms >>> did it go away. Today they are trying again. What I wanted to know is how >>> are you getting along with the latest update. I am using the old SE. >>> >>> Many thanks >>> >>> Judy >>> >>> Sent from my iPhone >>> >>>>> On 28 Aug 2020, at 23:16, Joshua Hendrickson wrote: >>>> >>>> Alan is correct. I also have the exchange this title option if I >>>> enter on the menu of an audible book. However, I always have to call >>>> anyway if I want to exchange a title because I just can't return a >>>> book not even from the audible website. It has never worked for me >>>> except to phone. The option to phone audible is even in the app when >>>> I'm told I can't return a book. But the initial exchange this title >>>> is deffinately in my audible app. >>>> >>>>> On 8/28/20, Mary Otten wrote: >>>>> Well, Michael, I am in the states, and I don�t have that option. I have >>>>> all >>>>> of the other options, including send this book and add to favorites, but >>>>> exchange is definitely not there. Multiple books on more than one phone >>>>> show >>>>> zip. Maybe it�s because I get all my credits at once? Seems very odd. >>>>> >>>>> >>>>> Sent from my iPhone >>>>> >>>>>> On Aug 28, 2020, at 2:55 PM, Michael Feir >>>>>> wrote: >>>>>> >>>>>> ? >>>>>> I think a couple of those options, "sendd this book" and "exchange this >>>>>> title" are only available in the US currently. I'm Canadian and need to >>>>>> either call Audible or go to the full desktop version of the Auydible >>>>>> site >>>>>> and into "purchase history" in order to return titles. A dialogue opens >>>>>> up >>>>>> over the page once you double tap on "return" and then you need to >>>>>> navigate that dialogue. Not too hard at all. I like the thought of >>>>>> being >>>>>> able to return books from right in the app so I hope they extend that >>>>>> option to Canada. >>>>>> >>>>>>> On Fri, Aug 28, 2020 at 5:42 PM Richard Turner >>>>>>> wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >
Re: for Joshua
Thank you so much Joshua and Diane, perhaps i will take the plunge and update. Will it slow my little old SE down for a bit for a while. Judy Sent from my iPhone > On 29 Aug 2020, at 13:56, Diane Giannetti wrote: > > It really is a good idea to keep your phones updated. One of the main reasons > is Security. Another one is each time the update happens, there may be some > bugs, but, it’s not that bad at the phone cannot be operated at all. > > Sent from Diane's awesome iPhone! > >> On Aug 29, 2020, at 8:45 AM, Joshua Hendrickson wrote: >> >> Well, the good news is, I don't really mind the new update like I >> thought I would. The only reason why I updated, was it seemed like >> apple did the update, and I had to enter in my touch ID. I didn't >> have the option of saying later. There is this weird tapping thing >> that might happen when you update. You will feel it when you swipe on >> the screen. Just call apple accessibility and they will help you get >> rid of that. You won't be able to check the status bar to see the >> battery level of a bluetooth device. You have to go to battery on >> page one of your phone to see that. Although, usually I can just ask >> Siri current battery level and she will tell me the battery level of >> my iPhone and a bluetooth device. If you have to update, good luck. >> It really isn't that bad. >> >>> On 8/29/20, Judy Pryor wrote: >>> Hi Joshua, i thought of you last night when Apple seemed to be forcing me to >>> update . I am still on 12.4.1. It was only when I disagreed with the terms >>> did it go away. Today they are trying again. What I wanted to know is how >>> are you getting along with the latest update. I am using the old SE. >>> >>> Many thanks >>> >>> Judy >>> >>> Sent from my iPhone >>> > On 28 Aug 2020, at 23:16, Joshua Hendrickson wrote: Alan is correct. I also have the exchange this title option if I enter on the menu of an audible book. However, I always have to call anyway if I want to exchange a title because I just can't return a book not even from the audible website. It has never worked for me except to phone. The option to phone audible is even in the app when I'm told I can't return a book. But the initial exchange this title is deffinately in my audible app. > On 8/28/20, Mary Otten wrote: > Well, Michael, I am in the states, and I don’t have that option. I have > all > of the other options, including send this book and add to favorites, but > exchange is definitely not there. Multiple books on more than one phone > show > zip. Maybe it’s because I get all my credits at once? Seems very odd. > > > Sent from my iPhone > >> On Aug 28, 2020, at 2:55 PM, Michael Feir >> wrote: >> >> >> I think a couple of those options, "sendd this book" and "exchange this >> title" are only available in the US currently. I'm Canadian and need to >> either call Audible or go to the full desktop version of the Auydible >> site >> and into "purchase history" in order to return titles. A dialogue opens >> up >> over the page once you double tap on "return" and then you need to >> navigate that dialogue. Not too hard at all. I like the thought of >> being >> able to return books from right in the app so I hope they extend that >> option to Canada. >> >>> On Fri, Aug 28, 2020 at 5:42 PM Richard Turner >>> wrote: >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> I just checked, and if you flick right once from the title of the book >>> and double tap on the button labeled Menu, The buttons are: >>> >>> Book Details, >>> >>> >>> Rate and Review, >>> >>> >>> Mark as Finished, >>> >>> >>> Exchange this title, >>> >>> >>> Send This Boo, >>> >>> >>> Add to favorites, >>> >>> >>> Cancel. >>> >>> >>> >>> >>> >>> >>> >>> HTH, >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> Richard >>> >>> >>> "He that cannot forgive others breaks the bridge over which he must >>> pass >>> himself,” and we forget that only grace can break the cycle of ancient >>> hatreds among peoples. (It is notable that while I have regretted not >>> granting >>> >>> grace to others, I’ve never once regretted extending it.)" - Edward >>> Herbert >>> >>> >>> >>> >>> >>> >>> >>> >>> On Aug 28, 2020, at 2:28 PM, Alan Lemly wrote: >>> >>> >>> >>> Mary, >>
Re: for Joshua
It really is a good idea to keep your phones updated. One of the main reasons is Security. Another one is each time the update happens, there may be some bugs, but, it’s not that bad at the phone cannot be operated at all. Sent from Diane's awesome iPhone! > On Aug 29, 2020, at 8:45 AM, Joshua Hendrickson wrote: > > Well, the good news is, I don't really mind the new update like I > thought I would. The only reason why I updated, was it seemed like > apple did the update, and I had to enter in my touch ID. I didn't > have the option of saying later. There is this weird tapping thing > that might happen when you update. You will feel it when you swipe on > the screen. Just call apple accessibility and they will help you get > rid of that. You won't be able to check the status bar to see the > battery level of a bluetooth device. You have to go to battery on > page one of your phone to see that. Although, usually I can just ask > Siri current battery level and she will tell me the battery level of > my iPhone and a bluetooth device. If you have to update, good luck. > It really isn't that bad. > >> On 8/29/20, Judy Pryor wrote: >> Hi Joshua, i thought of you last night when Apple seemed to be forcing me to >> update . I am still on 12.4.1. It was only when I disagreed with the terms >> did it go away. Today they are trying again. What I wanted to know is how >> are you getting along with the latest update. I am using the old SE. >> >> Many thanks >> >> Judy >> >> Sent from my iPhone >> On 28 Aug 2020, at 23:16, Joshua Hendrickson wrote: >>> >>> Alan is correct. I also have the exchange this title option if I >>> enter on the menu of an audible book. However, I always have to call >>> anyway if I want to exchange a title because I just can't return a >>> book not even from the audible website. It has never worked for me >>> except to phone. The option to phone audible is even in the app when >>> I'm told I can't return a book. But the initial exchange this title >>> is deffinately in my audible app. >>> On 8/28/20, Mary Otten wrote: Well, Michael, I am in the states, and I don’t have that option. I have all of the other options, including send this book and add to favorites, but exchange is definitely not there. Multiple books on more than one phone show zip. Maybe it’s because I get all my credits at once? Seems very odd. Sent from my iPhone > On Aug 28, 2020, at 2:55 PM, Michael Feir > wrote: > > > I think a couple of those options, "sendd this book" and "exchange this > title" are only available in the US currently. I'm Canadian and need to > either call Audible or go to the full desktop version of the Auydible > site > and into "purchase history" in order to return titles. A dialogue opens > up > over the page once you double tap on "return" and then you need to > navigate that dialogue. Not too hard at all. I like the thought of > being > able to return books from right in the app so I hope they extend that > option to Canada. > >> On Fri, Aug 28, 2020 at 5:42 PM Richard Turner >> wrote: >> >> >> >> >> >> >> >> >> >> >> I just checked, and if you flick right once from the title of the book >> and double tap on the button labeled Menu, The buttons are: >> >> Book Details, >> >> >> Rate and Review, >> >> >> Mark as Finished, >> >> >> Exchange this title, >> >> >> Send This Boo, >> >> >> Add to favorites, >> >> >> Cancel. >> >> >> >> >> >> >> >> HTH, >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Richard >> >> >> "He that cannot forgive others breaks the bridge over which he must >> pass >> himself,” and we forget that only grace can break the cycle of ancient >> hatreds among peoples. (It is notable that while I have regretted not >> granting >> >> grace to others, I’ve never once regretted extending it.)" - Edward >> Herbert >> >> >> >> >> >> >> >> >> >>> On Aug 28, 2020, at 2:28 PM, Alan Lemly wrote: >>> >>> >>> >>> >>> >> >> >> >> >>> >>> >>> Mary, >>> >>> >>> >>> >>> >>> When I'm in my Library tab on the iOS Audible app and double tap the >>> Menu button to the right of one of my listed books, I get a list of >>> vertically stacked options one of which is Exchange this title. >>> >>> >>> >>> >>> >>> Alan Lemly >>> >>> >>> >>> >>> >>> -Original Message- >>> >>>
Re: for Joshua
Well, the good news is, I don't really mind the new update like I thought I would. The only reason why I updated, was it seemed like apple did the update, and I had to enter in my touch ID. I didn't have the option of saying later. There is this weird tapping thing that might happen when you update. You will feel it when you swipe on the screen. Just call apple accessibility and they will help you get rid of that. You won't be able to check the status bar to see the battery level of a bluetooth device. You have to go to battery on page one of your phone to see that. Although, usually I can just ask Siri current battery level and she will tell me the battery level of my iPhone and a bluetooth device. If you have to update, good luck. It really isn't that bad. On 8/29/20, Judy Pryor wrote: > Hi Joshua, i thought of you last night when Apple seemed to be forcing me to > update . I am still on 12.4.1. It was only when I disagreed with the terms > did it go away. Today they are trying again. What I wanted to know is how > are you getting along with the latest update. I am using the old SE. > > Many thanks > > Judy > > Sent from my iPhone > >> On 28 Aug 2020, at 23:16, Joshua Hendrickson wrote: >> >> Alan is correct. I also have the exchange this title option if I >> enter on the menu of an audible book. However, I always have to call >> anyway if I want to exchange a title because I just can't return a >> book not even from the audible website. It has never worked for me >> except to phone. The option to phone audible is even in the app when >> I'm told I can't return a book. But the initial exchange this title >> is deffinately in my audible app. >> >>> On 8/28/20, Mary Otten wrote: >>> Well, Michael, I am in the states, and I don’t have that option. I have >>> all >>> of the other options, including send this book and add to favorites, but >>> exchange is definitely not there. Multiple books on more than one phone >>> show >>> zip. Maybe it’s because I get all my credits at once? Seems very odd. >>> >>> >>> Sent from my iPhone >>> On Aug 28, 2020, at 2:55 PM, Michael Feir wrote: I think a couple of those options, "sendd this book" and "exchange this title" are only available in the US currently. I'm Canadian and need to either call Audible or go to the full desktop version of the Auydible site and into "purchase history" in order to return titles. A dialogue opens up over the page once you double tap on "return" and then you need to navigate that dialogue. Not too hard at all. I like the thought of being able to return books from right in the app so I hope they extend that option to Canada. > On Fri, Aug 28, 2020 at 5:42 PM Richard Turner > wrote: > > > > > > > > > > > I just checked, and if you flick right once from the title of the book > and double tap on the button labeled Menu, The buttons are: > > Book Details, > > > Rate and Review, > > > Mark as Finished, > > > Exchange this title, > > > Send This Boo, > > > Add to favorites, > > > Cancel. > > > > > > > > HTH, > > > > > > > > > > > > > > > > > > > > > Richard > > > "He that cannot forgive others breaks the bridge over which he must > pass > himself,” and we forget that only grace can break the cycle of ancient > hatreds among peoples. (It is notable that while I have regretted not > granting > > grace to others, I’ve never once regretted extending it.)" - Edward > Herbert > > > > > > > > > >> On Aug 28, 2020, at 2:28 PM, Alan Lemly wrote: >> >> >> >> >> > > > > >> >> >> Mary, >> >> >> >> >> >> When I'm in my Library tab on the iOS Audible app and double tap the >> Menu button to the right of one of my listed books, I get a list of >> vertically stacked options one of which is Exchange this title. >> >> >> >> >> >> Alan Lemly >> >> >> >> >> >> -Original Message- >> >> >> From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On >> Behalf Of Mary Otten >> >> >> Sent: Friday, August 28, 2020 2:21 PM >> >> >> To: VIPhone via >> >> >> Subject: Returning or exchanging audible books using the iOS audible >> app >> >> >> >> >> >> Someone in a WhatsApp group I am part of says that he is able to >> exchange audible books from within the iOS audible app. If you go to >> your library, get the list of books that you have downloaded, and >> double >> tap on the menu next to one of those books, >>
Re: for Joshua
Hi Joshua, i thought of you last night when Apple seemed to be forcing me to update . I am still on 12.4.1. It was only when I disagreed with the terms did it go away. Today they are trying again. What I wanted to know is how are you getting along with the latest update. I am using the old SE. Many thanks Judy Sent from my iPhone > On 28 Aug 2020, at 23:16, Joshua Hendrickson wrote: > > Alan is correct. I also have the exchange this title option if I > enter on the menu of an audible book. However, I always have to call > anyway if I want to exchange a title because I just can't return a > book not even from the audible website. It has never worked for me > except to phone. The option to phone audible is even in the app when > I'm told I can't return a book. But the initial exchange this title > is deffinately in my audible app. > >> On 8/28/20, Mary Otten wrote: >> Well, Michael, I am in the states, and I don’t have that option. I have all >> of the other options, including send this book and add to favorites, but >> exchange is definitely not there. Multiple books on more than one phone show >> zip. Maybe it’s because I get all my credits at once? Seems very odd. >> >> >> Sent from my iPhone >> >>> On Aug 28, 2020, at 2:55 PM, Michael Feir wrote: >>> >>> >>> I think a couple of those options, "sendd this book" and "exchange this >>> title" are only available in the US currently. I'm Canadian and need to >>> either call Audible or go to the full desktop version of the Auydible site >>> and into "purchase history" in order to return titles. A dialogue opens up >>> over the page once you double tap on "return" and then you need to >>> navigate that dialogue. Not too hard at all. I like the thought of being >>> able to return books from right in the app so I hope they extend that >>> option to Canada. >>> On Fri, Aug 28, 2020 at 5:42 PM Richard Turner wrote: I just checked, and if you flick right once from the title of the book and double tap on the button labeled Menu, The buttons are: Book Details, Rate and Review, Mark as Finished, Exchange this title, Send This Boo, Add to favorites, Cancel. HTH, Richard "He that cannot forgive others breaks the bridge over which he must pass himself,” and we forget that only grace can break the cycle of ancient hatreds among peoples. (It is notable that while I have regretted not granting grace to others, I’ve never once regretted extending it.)" - Edward Herbert > On Aug 28, 2020, at 2:28 PM, Alan Lemly wrote: > > > > > > > > Mary, > > > > > > When I'm in my Library tab on the iOS Audible app and double tap the > Menu button to the right of one of my listed books, I get a list of > vertically stacked options one of which is Exchange this title. > > > > > > Alan Lemly > > > > > > -Original Message- > > > From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On > Behalf Of Mary Otten > > > Sent: Friday, August 28, 2020 2:21 PM > > > To: VIPhone via > > > Subject: Returning or exchanging audible books using the iOS audible > app > > > > > > Someone in a WhatsApp group I am part of says that he is able to > exchange audible books from within the iOS audible app. If you go to > your library, get the list of books that you have downloaded, and double > tap on the menu next to one of those books, > > you get a bunch of choices, one of which is supposed to be return or > exchange this book. I have tried this, not because I wanted to exchange > something, but just because I wanted to see if I have a choice. And I > don�t. The books I tried it on or a couple of > > recently purchased books. So they definitely met the criteria for > possible exchange. But I�m not seeing this choice. Is anyone else seeing > it? > > > > > > > > > Sent from my iPhone > > > > > > -- > > > The following information is important for all members of the V iPhone > list. > > > > > > If you have any questions or concerns about the running of this list, or > if you feel that a member's post is inappropriate, please contact the > owners or moderators directly rather than posti
