Apple Releases iOS 8.1.2
Apple today released iOS 8.1.2 as an over-the-air software update.
This update reportedly includes a number of bug fixes, including a fix for a problem regarding ringtones purchased through the iTunes Store. Apple advises users who have lost ringtones to restore them by visiting https://itunes.com/restore-tones from their iOS devices.
iOS 8.1.2 was not seeded to developers before being released to the public, so we do not know at this point whether it includes any fixes or improvements for blind and low vision users. Please let us know in the comments of any changes that you find.
When I tried visiting the address afterupdating to restore my tones, I saw a bunch of ring tones and could not figure out how to locate the tones I've bought. Am I missing something?
I figured out my problem. to date, ring tones bought on an older phone or just a different device still cannot be restored as they are somehow bound to the sim card for that device. I bought ring tones on my iPhone 4S, and of course don't have access to them anymore uon my 5S. I was hoping that this restriction was lifted but I guess not.
It's early, but I have yet to notice anything different in iOS 8.1.2, at least nothing obvious. The Safari bugs are still present, so those hoping for improvements there will be disappointed.
For what it's worth, the update reset my network settings, so I had to reconfigure my iPad for our Wifi network.
that's odd, it didn't reset either my iPhone nore my iPad mini's network settings.
and yes, to the poster about ringtones. that's still the case. bit stupid, in todays world, but that's apple for you. lol
as for changes, i think i have found one. it seems to have fixed, or at least fixed for now, the keyboard positioning in the spotlight search screen. in landscape, the keyboard is now along the bottom, as should be, as aposed to standing on end on the side. lol
that was sposed to be fixed in the previous updat,e but it didn't seem to stay fixed. so lets see if it stays fixed this time.
"The Safari bugs are still present, so those hoping for improvements there will be disappointed."
the fact they have not fixed the safari bug is completely inexcusable and unacceptable. we're not talking about some fancy or add-on features, it is web browsing, and it is the most basic part of the operating system.
if the mail app had problem accessing gmail, it would be fixed within days. and imagine customers' phone got locked up, screen black in the middle of browsing the web? i imagine it would be fixed within hours.
lack of resources is bs, for a 700 billion company? give me a break! actually, i'm willing to buy the bs if they could fix this in a reasonable period of time, say 2 weeks or even a month. we're 3 months int the release of iOS 8, soon we'll be talking about iOS 9 and WWDC. just imagine someone bought a new shining iPhone and can't even browse the web?
i don't want to be harsh, because i don't feel good being harsh, but this is really too bad!
I noticed that my 6 Plus is not crashing as much after updating to iOS 8.1.2. Hopefully it stays this way, and its not just a temporary relief.
Something not happening as much does not count. It is most likely you wanting something to be the case so you think it is.
Not happening as much means it is still happening and not fixed. Why bother saying something like that? It is not fixed until it does not happen at all.
I really dislike people saying things like this is not happening as much or it seems to be occurring less; No it's not; Its just wishing that it would stop.
Soon, Windows 10 will be released and it will be a universal os on all platforms such as PCs, Tabs, and Phones. WHen that happens, a user can install and run Jaws on their phone and use it. I know really know about the Jaws touch interface, and frankly, Jaws has its issues. But it will be another option for accessibility and worth looking into.
If the bugs are not being fixed within a reasonable amount of time, it does make it difficult to feel comfortable with IOS and its continual use.
The more choices we get in terms of accessibility, the better for everyone in the end.
So here is hoping.
And I am no fan of Capitalism and the so-called benefit of competition. Its not that JAws will be competing with anyone. Its just that a platform will be released for Jaws to run again. I despise their +1000 for a license model, but I do own one so...
Not just Jaws, but Window Eyes and System Access as well.
This is why I have them in my iTunes. I went from iPhone 4s, 5, 5s and my Iphone 6 without no issues tranfering my ringtones. I save them also in my PC in dropbox to be save.
Hi.. One thing I noticed about the new update is that my phone app wouldn't open _at _all! It was a wacky bug, and I'm not sure anyone mentioned it yet.. But when I double tapped the "phone" icon on my iPhone 5, it would just jump me up to the top of the home screen... Frustrating.. Finally, I asked Ciri to open my phone, and it did... I then closed it, and tried to open it again by double tapping it, and it worked. Goofy, but that's what happened..
Otherwise, the ringtones still disappeared after I tried to restore them.. I ended up with duplicate copies of each tone.. Finally, I just went through my iTunes library to get them all back..
I don't mind people saying that something does not happen as often as it did with the last upgrade to firmware or to a program, because it means that the attempt to fix a bug is on the right track. If you remember the song "The Blizard", at first, it's only 7 miles to Mary nne. Near the end of the song, "It's just a hundred yards to Mary Ann." When traveling through a blizard and freezing, which would you rather be? Same goes for trying to fix a bug. Sure, it's still happening, but you seem to think that it is the user imagining that the situation is better? This is not necessarily the case. If it used to crash 80 percent of the time and now only 50 percent of the time, this is not someone's imagination.
So you believe that an individual who is saying that it doesn't seem like its happening as much is sitting there, and measuring a difference between 80% and 40%?
Yes, I believe its a placebo simply because people want to believe that something is gone or at least a little less. Recently, I have noticed that two finger scrubbing results in less navigation locks and voiceover freezes. However, its plaguing others, and is still happening to me regularly. Its probably that I have subtly changed my usage and/or am some other factor that I am not aware. The problem persists and will persist until it is gone completely.
Apple doesn't half way fix things. Doing so would be a waste as it will prevent understanding how a bug truly works and needs to be resolved. Apple either completely fixes a bug or leaves it to be fixed on a different firmware update. THEY DO NOT JUST MAKE AN ISSUE 80% of the time to 50% of the time. There is no logic in that whatsoever.
IF something is occurring less, its because of some accidental programming which results in in less occurances. BUT, one person noticing lower occurances because they do while no one else does means the bug still exists, and needs to be fixed. IT does not mean that things are better.
Someone doesn't care if they have half cancer or whole Cancer; they just want the entire cancer to be gone.
You have every right to use whatever metaphor you wish. But Unless an individuals usage is actually recorded and compared to past usage, and then compared to others' usage, its all subjective and here say.
I only bank on a bug being completely gone. One person saying it is happening less to them with no explanation as to why and examples of why they think so does not demonstrate that a bug is fixed or being fixed. It only irritates me because it shows that the bug has not been fixed and the poor people who suffer through have to continue to do so.
I don't see the relevance of your song in a tech blog discussing a new version of IOS. This is meant to discover if bugs have been removed, not if maybe this or that. The bugs have either been removed or they are still there.
I guess I really shouldn't be surprised (and yet, for some reason, I still am) that you are discounting the improvements other users are finding simply because you haven't experienced it yourself.
I saw a report on Twitter that the "Safari back bug" was fixed in iOS 8.1.2. Is it fixed for everyone? I have no idea. Is it fixed for the user who reported it? I have no doubt.
I guess what I'm trying to say here is...who are we to say that another person is or isn't experiencing fixes on their device? How would we know, for example, whether another user is--or is not--experiencing fewer crashes? We don't have any other way of knowing, other than to take their words at face value. It's their device, afterall...
If people are finding updates to be subjectively better or worse, great. As a community, though, I'm uncomfortable with the idea that the only fixes some take seriously are those which can be quantified with hard data. Again, nobody knows a device better than the device's primary user.
There is no reason to assume one cause is associated with one, and only one effect.
There is no reason to assume one effect is associated with one, and only one, cause.
An issue may be precipitated by more than one problem, and, fixing one of those problems could reduce the number of incidents without eliminating them altogether.
I have to agree with Michael and the last poster on this thread. Just wow. I did'nt personally have many bugs when I upgraded to iOS 8 when it first came out, unless you count the siri thing, and that was fixed in a couple previous releases if memory serves me right. And I've never really brouzed the web on my phone so I don't know if bugs were fixed or not. But I digress.
I am in total agreement with Michael and the posters after him. Yes, safari does have it's issues, but it's not a deal breaker for me. If you wanna switch to a windows phone, fine. whatever accessibility option works for you, then go with it. Just be glad your iPhone has accessibility built right into it. But, back to safari. Yes, it has the same issue as safari does on the Mac side when on certain pages. Just reload the page, thats simple enough, and it's a work around. And, I too, have not had much trouble with iOS8.1.2 yet either.
Vash, it appears that we need to publicly remind you that one of the primary reasons that AppleVis exists is for people to provide support to each other. It most certainly does not exist to provide you with a platform to attack people because their experience or opinion is not what you believe it should be.
Personally, I can think of past occasions where a software update has provided an incremental or partial resolution to a problem. Feel free to tell me that I am deluded and stupid for believing this. However, be aware in advance that your attitude and responses on this site to other people who don’t share your views or jump to your commands is getting you very close to having your account removed. So, consider this post as a line in the sand.
I thought there were lots of posts about this update but alas, it's just more blind bickering.
David and Michael, I completely agree with you. Frankly, if a new member were to read Vash's antics, him or her is going to feel uncomfortable posting despite them having a fix, tipcs and tricks or what ever to contribute to the larger discussion on hand. I'm surprised his account hasn't been deleted despite the fact that he has attributed this negativity repeatedly. I would hate that the community is potentially missing out on some incredible nugget of whisdom due to a single user.
Vash and i have disagreed, big shocker. However, its attitudes such as his, no room for apology, or even a I was wrong, I'm done. I don't want to post, and that's unfair to everyone else who wants to, or needs to ask a question. It's topics like this that get so many comments that make a question I may have say about Knfb reader get buried and I never get an answer. Plus, it's just not enjoyable anymore to post. Ok back to the update. It was never promised to be a fix, it was a few speciffic bugs. Plus the file size was small, so realistically how much can they fix? Now i don't know about the code, so maybe my last point is wrong. Frankly, if vash's account is removed, this community would be happier. As it is, were it possible for the user to deactivate their own account, mine would have been ages ago.
I sometimes wonder if Vash and a few others don't simply use Applevis as a means of being nothing but negative. If you're so incredibly dissatisfied with Apple, then why on earth do you continue to use their products? So you can come on here and continue to bash them? Probably. These comments are the most unhelpful things I've seen so far. If I was a new user considering buying an iPhone I'd run away very fast and not look back. Do you want that to be how it is for someone? Think before you complain so much. Apple has offered a product that has advanced many people's lives and offered them many opportunities they can't even imagine, and you're over there arguing about wether a bug in Safari happens some of the time or less of the time? Come on, guys, you're losing your heads and losing the grasp on the big picture. I'm sorry apple didn't fix something that was, aparrently, important to you. Go buy a droid or a Windows phone if you hate Apple so much.
Without engaging in the ancillary discussion in this thread, please permit me to observe that one reason your posts might not get answers is that no one *knows* the answers. I see this all-too-often on many email lists: someone will post a question, not hear for several days and then panic, thinking that either people are stonewalling or that his/her post didn't get to the site. Usually, the simple truth is that no one knows the answer to the question and most people are sufficiently intelligent that they don't want the list or blog thread or whatever cluttered up with "I don't know"s or "Haven't a clue"s.
You might go to NFBNET.ORG and subscribe to the Reader-Users list. I know for certain that developers and support personnel at KNFB Reading Technologies monitor that list diligently.
I'm a new user of the site and would just like to emphasize the valuable resource it represents. In that spirit, I don't think that negative comments, discussion and debate constitutes a beneficial use of the community platform. I can understand peoples frustration with particular bugs, but realistically it may be until 8.2 when the back button issue with Safari is addressed correctly. I would urge patience, restraint and respect for individuals perspectives and opinions, arguing won't amount to anything productive, and certainly won't resolve the remaining bugs.
With best wishes to all,
Just don't think that there are any fixes for 8.1.2
Its probable that 8.2 is the one that will hold potential.
Darren12 , thanks for the kind words. Also you are COMPLETELY CORRECT.
There are a lot of bugs. And a lot of people with different views. We should be helping one another and being productive
I actually think that if there were bug fixes, Applevis crew would have made a post. They did it for 8.1.1, reported bugs for 8 and 8.1,
Vash, we have no more information than anybody else outside of Apple as to what fixes were rolled out in 8.1.2.
Even in the cases where we have access to a developer release of an update before it becomes publicly available, it’s still impossible for us to be anywhere close to definitive on what fixes it may or may not contain … there are simply too many possible combinations of hardware, third party apps and unique ways that people use their devices. As always, we rely on the wider community to identify and confirm any fixes.
Actually, the fix for replacing purchased ring tones was significant for me, because I purchased a couple ringtones from the iTunes store, but every time I rebooted my phone or something else happened I'm not sure? but when I would receive another call it went back to the default ringtone and it's as if the tone disappeared. This last update fixed that problem and all my tones are restored now. So an update doesn't always have to relate to the accessibility aspect of it, like I said some of you guys need to get a grasp on the big picture. I fully understand that a release should be bug-free, but asking for that is like nearly impossible for all the reasons Michael stated above. There are so many combinations of settings and other ways people use their phones that it would be impossible to fix every single bug that pops up. What we have to do is work around the bugs and make things work. Like I said earlier, coming on here and being all snarky doesn't fix anything in the grand scheme of things. It might make you feel better, but the bugs still aren't fixed. I'm not having any problems at all with 8.1.2 and I know others aren't either. We all use our phones and devices differently.
Safari works perfectly for me on a 5s.
Huh, interesting. Thanks austin for your feedback on safari. Just out of curiosity, did you try applevis's website? I'm just wondering because on my mac with the latest updates to safari and the os, I have to reload the webpage when going back to previous applevis pages.
Safari sometimes works on the 6 Plus now, but the back gesture hasn't been fixed completely. The refresh button is still the current work-around I use though. As for switching to another platform, maybe people should do their research before bashing Apple's products and claiming to switch. For one, you won't be able to use JAWS, System Access, or NVDA on a Windows Phone, because they do not use Intel or similar processors. Just thought I'd let everyone know about that. I apologize for mentioning Windows Phone once again on this post.
Bluetooth keyboard bug still remains as it was. Keyboard is still not found in the text field on IPhone 5S. Hope apple will fix this in the next update.
I suspect that part of the problem lies in my observation that sighted folks don't usually seem to know where the Back Button is but only know how to click forward. Wonder how many Apple techs know how to use their Back buttons? :-)
I have the bug where using the back button causes the page to not work until I use the refresh button, but I have never heard of or experienced the one where you can not navigate back up to the top of the page by heading from the bottom of the page. If I scroll to the bottom of the page I can navigate back up without ever having any issues.
A 4 finger tap at the bottom of the screen has never ever gotten me to the bottom of a webpage. Is it supposed to? I sure wish it would. It only puts focus at the bottom of the screen, which is easy enough to do with one finger.
Actually, the elimination of the bug where navigating by headings sometimes threw you to a random place in the page was the best thing about iOS8 for me. I prefer refreshing the page sometimes to frequently being unable to get to a certain spot on the page, which happened all the time with iOS 6 and 7.
I'm still having a problem where I can't move the last row of apps on my iPhone 5. This is under 8.1.1, but I had to move apps on an iPhone 4s running 8.1.2, and the problem is present there as well, it seems. I've been able to move apps on my iPad. I'll try putting my phone in landscape and try moving apps like that next.
Keep in mind while jaws may be able to run on phones using windows10, unless something changes, unlike voiceover these phones will not be accessible out of the box and I'm betting you will have to have sighted assistants to install it, unlike a pc where you can set it up using narrator by pressing the hotkey until you can get far enough to install jaws because accessing narrator using a touch screen without sighted help is probably going to be impossible for a blind user.
Just my 2 sence for those that are frustrated with apple and thinking about switching. I don't know about you but I like my independants in setting up things myself.
Not only that but you will have to purchase a licence for jaws to work on your mobile phone kind of like back in the days of mobile speak or talks.
Tip for iPad users. I've found that a five finger up brings up the app switcher, no longer four fingers, all the other swips work the same. Also, if swipes are not working for you, lock the screen and unlock it again, I've found that this fixs the problem. That, or just use the home button. Show it some love. Smile.
Has anyone found that when you send or receve an audio message, it's hard to flick back through other messages untill the audio message or messages expire and go away?
I've definitely encountered this.
Also, while responding to a message with out unlocking the screen, my phone slows right down. VO becomes very laggy and I haven't been able to use dictation at times. Now, I simply avoid that until its been fixed.
What iPhone are you using? Sometimes that happens to me, sometimes it doesn't though. It's very strange.
I'm using it on an iPhone 5s
Jesus R, do you have your display view set to zoom? I had mine on zoom and had the same problem moving aps you did. But I changed the view to standard, and there is no issue anymore. If you change the view to standard, the app icons get smaller and there will be a sixth row for apps above the dock. You can change the view by going to settings, display and brightness, and then there is a heading called display zoom. the button under that heading for you should say view zoom. tap that and change it to view standard. It won't change which pages your apps are on, there will just be a new blank row at the bottom of each page right above the dock.
I'm on an iPhone 6 though. I don't know what the differences are in the number of rows on your 5 because I went straight from 4s to 6.
I believe the 5, 5C and 5S all share the same screen, so 5 rows per home screen page.
i think it was the first release of ios8 that broke table headers and it doesn't appear to be fixed yet. if you have properly formed html that has table headers, <th> tags, those labels are not being read when you navigate to different cells in the table. it worked fine in ios7.
has anyone heard whether this issue is being worked on?
No idea on when tables will be fixed with web content. Yes, I was experiencing this with a delivery service online on my mac the other day. I had to use the links for a delivery window, and then the table worked fine.Anyway, no idea on when they will be fixed in the next update or not. Sorry to say, but we won't know that till the update comes out whenever that will be.
HTH, and good day.
I haven't noticed this being reported in the bug lists for 8.0 or 8.1.1, but it's possible I missed it.
In the Messages app on iOS 8.1, there is a VoiceOver accessibility issue with the "Attach Media" feature. I have verified it on an iPhone 4S running 8.1.2, and an iPhone 5C running 8.1.1.
After a long hold on "Attach Media", which brings up the video camera ready to shoot, there is a button labeled "CameraToggle". Presumably, that switches between front and back camera. However there is no spoken feedback on which camera is being used at any given time.
This should be more like the "Camera Chooser" button normally available in the camera app, which speaks the currently selected camera.
As it stands, there is no way to determine which camera is going to be used. I reported this to Apple Accessibility today.
Last week, I upgraded from iOS 7.0.6 to 8.1.2 on my iPhone 4S. Almost immediately, I experienced the homescreen rearrangement bug that has been talked about here many times. But only for certain apps. The upgrade installed the Health and Tips apps, both on the bottom rows of their respective homescreens.
If a factory-required app such as one of those is in the bottom row on any home screen (above the dock), it can not be moved to
any other location with Voiceover running.
This is true even if I enter homescreen editing mode by first trying to move another app.
If the movement of another app causes the factory-installed app to move out of the bottom row, it is then possible to directly move the factory app.
All of this is also true for folders: they won't move, either, if their in that bottom row. It is possible to put a factory app in a folder even though it won't move, but that is a dead end mostly.
I have only been in a position to notice this on the iPhone 4S, with four homescreen rows.