Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Does it fix the problem that i have with Keyboard Text replacements? On my iPad 2, my text replacement library disappeared when i upgraded to iOS 10. The list is fine on my iPhone 6 and Mac. I am able to add new entries on my iPhone or Mac and they synchronize back and forth with each other but the iPad seems to be entirely out of the synchronization loop. I have tried restarting the iPad as well as turning off and on iCloud services.

It did not fix the Keyboard Text Replacement synchronization issue that I have been experiencing. The synchronization is still not occurring on my iPad. Other things like Calendar, Notes, and Reminders are syncing just fine.

does anyone have suggestions on how to resolve this?

Did you include iCloud Drive when you turned iCloud services off and on? I had a similar issue awhile back when I turned iCloud Drive off for one of my devices (not knowing this is where the keyboard text replacements are stored). They came back once I turned iCloud Drive on again. If yours is already on, maybe try turning iCloud Drive off, rebooting, and turning it back on if you haven't already.

My other idea would be to add a new text replacement on the iPad and see if it syncs to the other devices. (This method worked for me when my passwords stopped syncing to one of my devices, so I just added a password on the affected device and the missing ones came in.)
 
Have you noticed any trends that kill your battery? For me, it seems to be Safari. For example, if I look at my battery usage over the last 24 hours - Safari has used 22% but has spent only 34 minutes on screen. Where as Music has been used for 6 hours but only used 18%.
Yeah, Safari has always been the battery hog for me, well before iOS 10. With my iPhone 7+ my battery life is better but Safari is still the battery hog.
 
I had a similar problem with Notes on my iPhone and iPad. the crashing did not occur until after i made a sketch in one of the notes. I removed the sketch from the note on my Mac. I was then able to open Notes on my iOS devices without a problem.

Thanks for telling me about that. I think the issue was Notes on my iPhone and Notes on iCloud became out of sync. I modified the note that I had most recently modified (easy to find since it sorts by when you last edit them) via the iCloud interface, and now Notes works on my iPhone again.

I wouldn't have bothered trying that if you hadn't said something. I was under the impression there was nothing I could do until Apple fixed a bug somewhere or uncorrupted a database or something.
 
They took too long with big-screens, and that opened the door for me to want more than the nickle-and-dime features they put out now (like press-and-pop or whatever that I couldn't care less about) or more importantly, the ones they remove (like the headphone jack).

How will you feel when Samsung removes the headphone jack on the Galaxy 8 or 9? It will happen, it's inevitable.
 
Don't blame me for your lack of reading comprehension. Seems you need to go back to whatever school you learned English from, and demand a refund.

I love discussing technology. You're the one still whining about liars or about my feelings. How amusingly hilarious.

I didn't say iPhone cannot multitask (although what it does is fancy app switching, but that's a whole 'nother conversation). I said I'd been able to do it for years...plural...before iPhone. And to be clear, I'm referring to split-screen multitasking.

So I ask again, remind me of when did iPhone come up with something (meaningful) ahead of Android?

On the other hand, never mind.

You'll waste my time with some other way to poke at my feelings, when the only one I feel is best represented by my profile pic.

Fancy App-switching? Another lie. iOS can multitask more than one App at a time where Apps in the background continue to run and are not paused. Do you even use iOS? How could you not be aware of this? And how could you not be aware of all the things iOS did before Android? You claim you like to discuss technology, but the fact you can't even think of a single thing iOS did first tells me otherwise.

A few things iOS/iPhone did first (ones with an * aren't even available on Android yet).

* Hardware on device encryption (back in 2009 with the iPhone 3GS). Android still using inferior software based encryption.
* NVMe for storage. Android phones still using UFS or eMMC, two vastly inferior technologies.
- 64bit processor. Not just a 64bit mobile processor, but a custom designed one. Took Samsung and Qualcomm almost 2 years to catch up with their own "custom" processors.
- BT 4.0 in the iPhone 4, the first mobile device on the planet that implemented it. This is what caused aftermarket accessory makers to start using it now that they have a mass produced device they could connect to.
- A proper permissions system. Even though Android finally added this, iOS is still superior. For example, in iOS I can have a permission as Yes, No or While Using. The While Using is a great addition which allows me to grant permission to something only while I'm actually in the App (like GPS, which won't let the App use it once I switch to another App).
- Activation Lock. Still superior to the Android version, which came out after. It's the single biggest reason smartphone thefts have dropped as it makes a stolen iPhone useless to a thief.
- MIDI support. Since iOS 4 and only added to Android 5 years later in Marshmallow.
* 3D Touch (pressure sensing screen). I mean a screen that can sense and measure pressure, not the stupid "fake" versions that measured the size of you finger to guess pressure or has sensors behind the screen to measure total on screen pressure).
* Low Latency Audio. Another one for musicians. iOS could do this back in iOS 4 while even brand-new Android flagships can still struggle to pass audio from App to App without incurring latency (which is unacceptable when recording).

These are just a couple quick ones I could come up with.
[doublepost=1474738547][/doublepost]
To be fair, he could be referencing a different form of multitasking than simply being able to play music in the background. Nougat brought with it split-screen functionality (complete with the ability to run the same app side by side) and video PIP for your smartphone. iOS might eventually give us that, but I can't deny that Android is currently better in that regard (for the small group of people who will eventually get Nougat at any rate).

He referred to iOS as a "fancy App switcher", which pretty much sums up his position (which is wrong).

My preference is for the Apple dev team to be given more time each year to release software that has less bugs, the current marketing timeframes are not realistic from a SDLC, hence we are seeing an increase of minor releases post launch. Thats all.

Did you seriously just type this? It's 100% impossible for you to release software without bugs. Especially when dealing with something as complex as an OS. No other operating system in the world (not even Windows with its huge market share) gets as many users onto the latest version as fast as iOS does (over 100 million in the first 24 hours). This means iOS 10 is running on a variety of devices on different carriers in different languages with users all having different settings and Apps installed. That presents a ridiculous number of combinations which is bound to cause some bugs to show up.

For me, I never had a single one of the issues people are reporting with iOS 10 and the iPhone 7. Neither did any of the numerous iOS devices in my house. Neither did anyone at work. I don't deny they exist for some users, but they are not the epidemic people make them out to be. People just don't understand the sheer scale of an iOS launch. They see 1,000 posts in an Apple support forum and think "Oh my God that's a lot of people with problems" without realizing it's only 1 out of 100,000 actual users (which is ridiculously low).

Even if the dev team at Apple was given more time, we would STILL see bugs at launch because it's simply not possible for them (or the beta users) to do enough testing to match 100 million actual users. At some point you have to commit to release the current version and deal with the issues later. Otherwise you'd never actually release anything.
 
  • Like
Reactions: PeteLP and frifra
It did not fix the Keyboard Text Replacement synchronization issue that I have been experiencing. The synchronization is still not occurring on my iPad. Other things like Calendar, Notes, and Reminders are syncing just fine.

does anyone have suggestions on how to resolve this?

Did you ever find a fix for this issue?
I'm experiencing the same thing..

After upgrading (OTA) to iOS 10 I lost all my text replacements on my 6S and iPad Air1. I added a lot of them back manually on my 6S, which was annoying, but they are not being synced to my iPad Air. And like you, I've also signed out of iCloud and then back in and turned iCloud backup off then back on and that did nothing.
 
Have you noticed any trends that kill your battery? For me, it seems to be Safari. For example, if I look at my battery usage over the last 24 hours - Safari has used 22% but has spent only 34 minutes on screen. Where as Music has been used for 6 hours but only used 18%.

Not really. The highest battery usage over the last 24 hours was a game I'd been playing for a while, which is exactly as I would expect to be at the top of the battery usage list.

I just find generally that my 6s Plus is using more battery in general, whether when its in sleep or when I have the screen on.

I should be getting my 7 Plus on Wednesday, so it will be interesting to see if I see the same with that.
 
Fancy App-switching? Another lie. iOS can multitask more than one App at a time where Apps in the background continue to run and are not paused. Do you even use iOS? How could you not be aware of this? And how could you not be aware of all the things iOS did before Android? You claim you like to discuss technology, but the fact you can't even think of a single thing iOS did first tells me otherwise.

A few things iOS/iPhone did first (ones with an * aren't even available on Android yet).

* Hardware on device encryption (back in 2009 with the iPhone 3GS). Android still using inferior software based encryption.
* NVMe for storage. Android phones still using UFS or eMMC, two vastly inferior technologies.
- 64bit processor. Not just a 64bit mobile processor, but a custom designed one. Took Samsung and Qualcomm almost 2 years to catch up with their own "custom" processors.
- BT 4.0 in the iPhone 4, the first mobile device on the planet that implemented it. This is what caused aftermarket accessory makers to start using it now that they have a mass produced device they could connect to.
- A proper permissions system. Even though Android finally added this, iOS is still superior. For example, in iOS I can have a permission as Yes, No or While Using. The While Using is a great addition which allows me to grant permission to something only while I'm actually in the App (like GPS, which won't let the App use it once I switch to another App).
- Activation Lock. Still superior to the Android version, which came out after. It's the single biggest reason smartphone thefts have dropped as it makes a stolen iPhone useless to a thief.
- MIDI support. Since iOS 4 and only added to Android 5 years later in Marshmallow.
* 3D Touch (pressure sensing screen). I mean a screen that can sense and measure pressure, not the stupid "fake" versions that measured the size of you finger to guess pressure or has sensors behind the screen to measure total on screen pressure).
* Low Latency Audio. Another one for musicians. iOS could do this back in iOS 4 while even brand-new Android flagships can still struggle to pass audio from App to App without incurring latency (which is unacceptable when recording).

These are just a couple quick ones I could come up with.
[doublepost=1474738547][/doublepost]

He referred to iOS as a "fancy App switcher", which pretty much sums up his position (which is wrong).



Did you seriously just type this? It's 100% impossible for you to release software without bugs. Especially when dealing with something as complex as an OS. No other operating system in the world (not even Windows with its huge market share) gets as many users onto the latest version as fast as iOS does (over 100 million in the first 24 hours). This means iOS 10 is running on a variety of devices on different carriers in different languages with users all having different settings and Apps installed. That presents a ridiculous number of combinations which is bound to cause some bugs to show up.

For me, I never had a single one of the issues people are reporting with iOS 10 and the iPhone 7. Neither did any of the numerous iOS devices in my house. Neither did anyone at work. I don't deny they exist for some users, but they are not the epidemic people make them out to be. People just don't understand the sheer scale of an iOS launch. They see 1,000 posts in an Apple support forum and think "Oh my God that's a lot of people with problems" without realizing it's only 1 out of 100,000 actual users (which is ridiculously low).

Even if the dev team at Apple was given more time, we would STILL see bugs at launch because it's simply not possible for them (or the beta users) to do enough testing to match 100 million actual users. At some point you have to commit to release the current version and deal with the issues later. Otherwise you'd never actually release anything.
This! Thank you! I'd give you 10 more likes if I could. Actually a fair comparison who was first with what feature between Android/iOS would be really interesting. Would be great if MacRumors would write such an article.
 
  • Like
Reactions: LinkedTriforce
Did you seriously just type this? It's 100% impossible for you to release software without bugs. Especially when dealing with something as complex as an OS. No other operating system in the world (not even Windows with its huge market share) gets as many users onto the latest version as fast as iOS does (over 100 million in the first 24 hours). This means iOS 10 is running on a variety of devices on different carriers in different languages with users all having different settings and Apps installed. That presents a ridiculous number of combinations which is bound to cause some bugs to show up.

For me, I never had a single one of the issues people are reporting with iOS 10 and the iPhone 7. Neither did any of the numerous iOS devices in my house. Neither did anyone at work. I don't deny they exist for some users, but they are not the epidemic people make them out to be. People just don't understand the sheer scale of an iOS launch. They see 1,000 posts in an Apple support forum and think "Oh my God that's a lot of people with problems" without realizing it's only 1 out of 100,000 actual users (which is ridiculously low).

Even if the dev team at Apple was given more time, we would STILL see bugs at launch because it's simply not possible for them (or the beta users) to do enough testing to match 100 million actual users. At some point you have to commit to release the current version and deal with the issues later. Otherwise you'd never actually release anything.

Did I just seriously type that? no need for the personal stuff :( Seems to happen a lot with your replies to me.

Maybe read what what I wrote. At no point did I say no bugs, its the severity. As you have pointed out in the past your background in debates, mine is software development for the past 20 years. Cute theory on how installation instances or user numbers impact software development....

Have a good day.
[doublepost=1474760126][/doublepost]
Do you understand that these fixes are just last minute fixes that happen with every hardware or major software release?

It has always been this way with every iOS release, it's nothing new. Grow up and stop looking at the past only with rose colored glasses.

Why is it wrong to want better QA software?

You do realise that rushing out a quick fix to a major issues, usually introduces other bugs in the process?

Anyway things are the way they are, so lets just agree that the current release process will continue . People who are concerned like myself can wait till 9.1 or 9.2 is out, and that will be much more stable
 
Last edited:
  • Like
Reactions: melendezest
Ever since i updated, my 7 gets stuck in an app an the only way to fix it is a hard reset
 
Did I just seriously type that? no need for the personal stuff :( Seems to happen a lot with your replies to me.

Maybe read what what I wrote. At no point did I say no bugs, its the severity. As you have pointed out in the past your background in debates, mine is software development for the past 20 years. Cute theory on how installation instances or user numbers impact software development....

Have a good day.

And where are these severe bugs in iOS 10? I've seen several minor ones that affected a small number of users and were quickly patched. Do you have a device that's unusable on iOS 10? That's what I'd call severe.

I've also been in software development for many years (since the early 80's). So please counter my "cute theory" and tell me why I'm wrong. Are you actually claiming that the incidents of bugs popping up is not related to how many people are using the software?


Edited: I have a few simple questions to get your opinion on:

1. Two people have the same iPhone 7 and the same version of iOS 10. Person A has a bug occur while Person B doesn't. What are a few possible reasons why one person is seeing the bug while the other isn't even though they're using the same App on the same iPhone and same version of iOS?

2. How many devices does a problem need to occur on before it's considered a bug? Does the issue need to be reproducible on every single device, or on a certain percentage of devices?

3. How often does a problem need to occur for a single person before you consider it a bug? For example, let's say I'm editing a photo and applying a filter. 99 out of 100 times it works, but 1 out of 100 times the program crashes applying the same filter.

I'm curious because these are real-world scenarios people face. Your buddy has an issue but you don't. You hear about problems online but you don't have it. Or you have a problem but it only happens rarely.
 
Last edited:
And where are these severe bugs in iOS 10? I've seen several minor ones that affected a small number of users and were quickly patched. Do you have a device that's unusable on iOS 10? That's what I'd call severe.

I've also been in software development for many years (since the early 80's). So please counter my "cute theory" and tell me why I'm wrong. Are you actually claiming that the incidents of bugs popping up is not related to how many people are using the software?

A minor bug will never go into a 0.0.x release.

Lets take the Lightning connected EarPods timing out bug, thats not minor, as it effects a major usability of the device. Moving on, given Apple knows exactly the hardware that is supported, the test case is to test all these hardware combinations. Lets say there are 100 combinations as a completely hypothetical example, a billion users makes no difference.... A hundred billion users makes no difference. As a development team its is your responsibility to test all scenarios. In the EarPods scenario, once you sell those 100units, your bug is uncovered.

In software development User size impacts performance/stress testing, capacity planning etc. You missing a bug in development will be uncovered by a very small user base. I use the EarPods example cause it does not take long for someone realise the controls are not working.

Saying that, User base can identify bugs for scenarios that you never planned for, and this does happen, though in the case of the EarPods, thats in apples control, they should have tested the combinations.

Interesting you consider the EarPod bug minor. Nor can you claim if affects a small user base, you have no idea how many combinations of that hardware/software have shipped.

Ill be honest , look, last few debates you were an expert on Audio, now software development, I'm really not interested in following this up. We have different ideas about software development, and in our Industry......there is a huge difference what is structured software development and cowboy approach, I've seen it all in 20 years. My worst devs had no concept of QA and saw no issues pushing code live....last thing on a friday before a weekend.
[doublepost=1474772751][/doublepost]
Nothing wrong, except it doesn't exist.

Its part of development, hence we strive for test driven development and automation to improve QA.
 
Its part of development, hence we strive for test driven development and automation to improve QA.

No big project is exempt from bugs.

Its just not going to happen, you don't see it anywhere else, and you would never see.
 
A minor bug will never go into a 0.0.x release.

Lets take the Lightning connected EarPods timing out bug, thats not minor, as it effects a major usability of the device. Moving on, given Apple knows exactly the hardware that is supported, the test case is to test all these hardware combinations. Lets say there are 100 combinations as a completely hypothetical example, a billion users makes no difference.... A hundred billion users makes no difference. As a development team its is your responsibility to test all scenarios. In the EarPods scenario, once you sell those 100units, your bug is uncovered.

In software development User size impacts performance/stress testing, capacity planning etc. You missing a bug in development will be uncovered by a very small user base. I use the EarPods example cause it does not take long for someone realise the controls are not working.

Saying that, User base can identify bugs for scenarios that you never planned for, and this does happen, though in the case of the EarPods, thats in apples control, they should have tested the combinations.

Interesting you consider the EarPod bug minor. Nor can you claim if affects a small user base, you have no idea how many combinations of that hardware/software have shipped.

Ill be honest , look, last few debates you were an expert on Audio, now software development, I'm really not interested in following this up. We have different ideas about software development, and in our Industry......there is a huge difference what is structured software development and cowboy approach, I've seen it all in 20 years. My worst devs had no concept of QA and saw no issues pushing code live....last thing on a friday before a weekend.
[doublepost=1474772751][/doublepost]

Its part of development, hence we strive for test driven development and automation to improve QA.

Not interested in following this up. That's because you're tired of me calling you out on some of the BS you post.

Look at my username - it tells you what I do for a living. And no, I don't read Import Tuner magazine and think adding a few boltons to a car makes me a tuner. I write firmware for engine control units (ECUs) used in cars. The two primary disciplines needed for this are software engineering and electrical engineering. Although I don't actually create the fuel/ignition maps for particular engines, I also have a pretty good understanding of this as well. Otherwise how could I write software that enables these engineers to do their jobs (extract maximum power/torque from an engine while ensuring smooth drivability, low emissions and good fuel economy)?

You posted BS about audio that anyone with a comprehensive electrical background would know is false. Being a huge audio fan coupled with my electrical background qualifies me to comment in this field. Just as my electrical background coupled with my automotive knowledge qualifies me to call Tesla vehicles average since (from my point of view) nothing in their cars is unique.

And I see you completely avoided the questions I posted. For good reason, because if you had answered them you would have been caught. Better to "walk away" from the conversation with the typical "let's agree to disagree" then to go further down this path. Just like you did in the audio discussion when I suggested we go deeper and discuss electrical theory as it relates to audio.


The type of software I write could be considered bug free. This is because the feature set is fixed and can remain that way for 5 years, the number of lines of code is orders of magnitude lower than something like an OS, I have no user-facing component to deal with and large portions of code have been eliminated over the years by FPGAs and custom ASICs. Even then I would never consider it to be 100% bug free, but it's pretty damn close.


I find it laughable that you're claiming Apple should find all these bugs before shipping along with your snide remark about the "cowboy approach", implying that either Apple and/or I do this. This has been debunked, but it gives you an idea of how reliable the software I write has to be. So I can guarantee you we don't fit the "cowboy approach", which means you must think Apple does.

http://www.snopes.com/humor/jokes/autos.asp-
 
Warning, this post is on-topic...

I took a trip with 10.01. Used my 3.5mm, 3rd party headphones with the adapter. Audio worked fine, but the volume control on the headphones did not. On the first three legs of the trip, no problem with airplane mode. After the final leg, I landed at PDX, saw a signal from T-Mobile, but got no data. Re-booted. No luck. But after driving home (and through different cell tower zones), everything was back to normal.

I loaded 10.02 and my 3.5mm headphone volume controls now work fine. Haven't tried airplane mode since updating.
 
Why is it wrong to want better QA software?

You do realise that rushing out a quick fix to a major issues, usually introduces other bugs in the process?

Anyway things are the way they are, so lets just agree that the current release process will continue . People who are concerned like myself can wait till 9.1 or 9.2 is out, and that will be much more stable
Getting out a fix to an (important) issue in a patch can certainly introduce something else, but that doesn't make it something that is "usually" the case.
[doublepost=1474785131][/doublepost]
Its part of development, hence we strive for test driven development and automation to improve QA.
We also strive for world peace (and have been for a long long time).

That said, it doesn't mean that most likely at least some things can't necessarily be improved in various places to one degree or another.
 
Last edited:
Went to my local Apple Store today and had to wait for half an hour after it opened before I got started with an Apple team member. I traded in my iPhone 6 ($200 to my cc) and bought a gold case iPhone 7. Took about half an hour to have him enter all the info to the point where my new iPhone 7 was ready to restore a iCloud backup. Took it home to finish the restore, pair my Apple Watch, set up my Apple Pay, download my apps, etc.

I've quickly come to love the new TouchID/Home spot - much nicer than the old button. The sound if great from the stereo speakers and the screen is outstanding. Should receive my new case from OWC later this week and TechArmor screen protector tomorrow. For now it's living in my old OWC case saved from the iPhone 6. Fits fine but the camera, flash opening isn't the right shape for the larger lens.





Apple today released the first official update to the iOS 10 operating system, just 10 days after releasing iOS 10 to the public and two days after seeding the first iOS 10.1 beta.

iOS 10.0.2 can be downloaded as an over-the-air update on all devices running iOS 10.

ios10-800x585.jpg

Today's update includes fixes for several minor bugs that have been discovered since the operating system was released.

A bug that caused the new Lightning EarPods designed for the iPhone 7 and 7 Plus to stop working properly has been addressed. EarPods have been timing out after a short period of time when listening to music, rendering the remote unresponsive and unable to control volume, access Siri, and answer phone calls.

The update also resolves an issue that caused Photos to quit for some users when activating iCloud Photo Library and fixes an issue that prevented enabling some app extensions.

iOS 10 is a major update that includes features like a redesigned Lock screen experience, a revamped Messages app with a full App Store, a Siri SDK for developers, new looks and features for Maps and Apple Music, and tons more.

Article Link: Apple Releases iOS 10.0.2 With Fixes for Headphone, Photos, and App Extension Bugs
 
I keep getting no service and dropping to 3G or 1x WTF on iOS 10
i hope this is the next fix its needed
 
Pure Comedy: "A bug that caused the new Lightning EarPods designed for the iPhone 7 and 7 Plus to stop working properly has been addressed. EarPods have been timing out after a short period of time when listening to music, rendering the remote unresponsive and unable to control volume, access Siri, and answer phone calls."
I can add to that: iOS 10 geared towards the "jackless" iPhone 7 managed to screw up bluetooth connections bigtime for me. Whenever I answer a phonecall in my car the iPhone takes over audio (like in ringtone via car-speakers, and the moment I pick up the audio is played back via the iPhone). The case is even more annoying when it comes to my cardo headset (in Helmet) the iphone randomly drops the connection, does not respond to audio-controls, makes up ones by itself (louder is my favorite, as it forces me to immediately turn of the headset or I will go half deaf and fully unaware of the traffic sounds around me)
So (in my pest impersonation of uncle Ben) along with courage apple shows great incompetence...thanks for that!!!
 
  • Like
Reactions: dan110
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.