-
All replies
-
Helpful answers
-
Sep 29, 2016 5:53 AM in response to mikaelfromhelsinkiby Meg St._Clair,mikaelfromhelsinki wrote:
Hi, how can I downgrade to 9.5? Custom personalized ringtones are very important to me.
Downgrading is not supported.
Which troubleshooting steps have you taken? As I noted above, my custom ring and text tones work just as they always have so, it's quite likely that you can fix this issue.
-
Oct 1, 2016 10:39 AM in response to Meg St._Clairby mikaelfromhelsinki,I have booted, re-installed. removed and installed ringtones. What else can I do?
I am not the only one;-)
-
Oct 1, 2016 1:59 PM in response to mikaelfromhelsinkiby Meg St._Clair,mikaelfromhelsinki wrote:
I have booted, re-installed.
Re-installed what?
Things that I'd consider trying would be deleting the account you sync your contacts too and then adding it back, restoring your phone from a back up, restoring as new.
-
Oct 1, 2016 5:54 PM in response to Meg St._Clairby mikaelfromhelsinki,I meant restoring. No help. I try to delete the account and add it back.
-
Oct 2, 2016 12:30 AM in response to Tilloneby Temetus,Same here. I have tried many different things to fix that issue, but it just ignores all the custom ringtones.
This should be BASIC stuff.
-
Oct 2, 2016 12:33 AM in response to Temetusby longtom99,You can try whatever you want!
IT IS A BUG and has to be fixed by Apple!
-
Oct 2, 2016 5:23 AM in response to longtom99by Meg St._Clair,longtom99 wrote:
You can try whatever you want!
IT IS A BUG and has to be fixed by Apple!
If it's a bug, why are so few people experiencing it?
-
Oct 2, 2016 6:03 AM in response to Meg St._Clairby iHese,it is a bug and it is in iOS 10 and in every phone. apple is fixing this.
-
Oct 2, 2016 6:09 AM in response to iHeseby Meg St._Clair,iHese wrote:
it is a bug and it is in iOS 10 and in every phone. apple is fixing this.
It is not happening on my iPhone 6 with iOS 10.0.2. I have both custom ringtones and custom text tones that work just fine.
-
Oct 2, 2016 6:20 AM in response to Meg St._Clairby Bernard Piller,It could be that only non-English (US) iPhones are affected
-
Oct 2, 2016 6:23 AM in response to Meg St._Clairby iHese,Yes it is. This bug is not about custom ringtones. Read the topic.
-
Oct 2, 2016 6:35 AM in response to iHeseby Meg St._Clair,iHese wrote:
Yes it is. This bug is not about custom ringtones. Read the topic.
I have been reading this thread since the beginning. This is the title of the topic:
IOS 10 and contact custom ringtones
I apologize if my response was unclear to your. I have custom tones selected for many of my contacts, both for ringtones and text tones. They all work fine.
-
Oct 3, 2016 6:47 AM in response to Meg St._Clairby _ALE_,Come on, I don't think that every single iPhone on earth must be affected by this problem to call it "a bug". And even if, whatever you may decide to call it, it's something never happened to any of us until this last major update.
Don't you think that Apple should at least say where did we went wrong if it's really our fault?
Ther are other threads in this forum with other people experiencing the same problem.
In Italy iPhone user forums are full of people complaining about that.
And I know that I'm not statistically relevant, but 10 people out 10 amongst iPhone user I know, is a "strange coincidence".
As an iPhone user the negation of my (and not so few others) problem is not the answer I expected.
-
Oct 3, 2016 7:07 AM in response to _ALE_by Meg St._Clair,_ALE_ wrote:
Come on, I don't think that every single iPhone on earth must be affected by this problem to call it "a bug". And even if, whatever you may decide to call it, it's something never happened to any of us until this last major update.
I never said it was. I was responding to someone who kept insisting that it is, in fact, happening to every iPhone 6. It's not.
Just to add to the completely irrelevant "statistics". I know about 15 people with an iPhone 6 and a couple with the iPhone 6+. I also support a whole lot more than that. I've yet to see it.
I'm not saying it's not real. What I'm saying is that it's most likely the result of some rare confluence of factors, only one of which might be iOS 10 that calling it an iOS 10 bug is premature.