I couldn't figure out why I kept accidentally opening the emoji panel, didn't think they would have done something as stupid as move it. I guess they did. Idiots. (yeah, I guess that includes me for not realizing they swapped the buttons)
Considering that Apple deals with a limited number of hardware configurations, unlike Android, it surprises me when some bugs weren’t intercepted before the first release.
In theory it is best to wait a month before installing, but I admit that I installed IOS12 immediately when it came out, luckily without obvious bugs, and featuring a noticeable boost in general smoothness of operation on my 4 year old 6 Plus, good enough to make me keep my phone for another year at least.
Hello? Public Beta. Been available for MONTHS.
But that still doesn't "beat" real life conditions with hundreds of millions of users.
Anyone who has written more complicated software than "Hello World" knows that.
Always interesting how initial IOS releases always follow up with a fix release soon after. But couldn't Apple just shouldn't we expect a better product the first time? If Apple is so great, then why not polish up your first release better?
Name me ONE OS that doesn't do that.
I'll wait.
Oh, right, Android; because there just ISN'T an Update for most people.
"Other bug fixes in this update include a reorientation of the "123" number key on the iPad, which was moved in the iOS 12 update and swapped with the emoji/language key"
This drove me nuts.
At least Apple listens to feedback and actually ACTS on it, unlike, say, Microsoft, which just keeps ramming bad ideas and silly UI paradigms down everyone's throat...
Aren't they supposed to have an advantage because they have only a few models to support and tightly controlled hardware?
Considering they are currently supporting something like EIGHT generations of iPhones (from the 5s to the Xs), 4 or 5 generations of iPads (iPad mini 4 and up, IIRC), plus the 6th gen iPod Touch (which constitutes the ENTIRETY of Apple's 64-bit mobile line), all of which have differences in radio hardware, SoCs, GPUs, etc., I wouldn't say that they have to support "only a few models" anymore.
It resolves an issue that could cause some iPhone XS devices not to charge when connected to a Lightning cable (...) Reports suggested multiple iOS 12 devices were affected rather than just the iPhone XS
Why phrase this in such a way? Can't you make a sentence that makes it clear from the beginning that it affects a number of iPhones and that's it?
Um, because there are iOS Devices other than iPhones...
I wish I hadn't. 12 also breaks progress syncing in iBooks with previous iOS versions, it took me a lot of digging to find that KyBook and PocketBook are the only reliable epub readers that work with older versions of iOS. Not to mention the new UI is pretty pathetic.
I actually like the new UI a bit better.
I am dissapointed in the sync not being backwards-compatible; but they have obviously changed their Library structure, and it would be inviting disaster to keep shuttling data-formats back and forth between "iBooks" and "Books" formats.
A shortage of cell towers in the mountains? Imagine that.
The issue is not the shortage of cell towers. It’s the fact that I had to restart the device every time I wanted to use it and had signal because the model would be in a bad state from the last time it lost signal and would not do anything whatsoever without a restart. That is not normal behavior. It should gracefully handle the loss and return of service without a restart.
Oh, and just in case they still haven't address the issue of "missing PDFs", I would suggest you save-off any PDFs you have stored in iBooks separately from your iTunes backup. Justin Case.
I might hold off on that if I were you. I am having serious radio issues with iOS 12 and I don't know that they are fixed in 12.0.1. I have a 7 and the radios will not let me do anything unless I have at least 3 bars. Also sometimes they just stop working until I restart the device. WiFi has been flaky as well. I was in the mountains this weekend and I basically had to restart my phone every time I wanted to use it. It seems the current radio firmware does not like when you have low reception.
So, you are recommending NOT upgrading to an OS version that announces fixes for some radio issues?
SO buggy code that apple fixed DOESNT count as a bug. WFT kind of STUPID BLIND apple WORSHIPPER logic if that? You are a disgrace
Sure.
Now, let's go back to Linux 0.09 and start adding up the bugs, shall we? Because that is EXACTLY the "standard" you are attempting to apply to WatchOS.
And no, bugs in code that are FIXED are NO LONGER COUNT AS BUGS.
Or has Linux been 100% bug-free since it was first foisted upon an unsuspecting world?
Over a year ago (don't recall exactly when, the book was published last December) I used a similar device in The Eridani Convergence when the protagonist hurls himself from a moving car (autonomous, and it had been hacked to kidnap him) in the middle of nowhere. He wakes up in a hospital room:
"How?" "How did we find you? Smart omniphone you've got there. Between the gee loads and the physiological changes it sensed in you -- good thing you had it on your wrist and not in a pocket -- it figured something was seriously wrong and started calling for help."
I like to think that someone at Apple read that and thought it was a good idea, but probably they were already working on it. Or they worked fast.;)
I can beat that by about 5 years.
In fact, when the iPhone first started having 3-axis Accelerometers, I considered making an "Emergency Call" App with built-in Fall-Detection.
Unfortunately, at the time (and maybe still), Apple prohibited that type of App from being published in the App Store.
But in this case, this instrinsic feature of WatchOS 5 is a obviously a LOT deeper-integration than a simple App can attain, even without the App Store restrictions. So it's an entirely different case.
Well, that proves it. Time to put it on over a million people's wrists without worrying about any false callouts.
The likelihood of significantly high numbers of truly false "Callouts" is drastically reduced by the fact that the Watch counts-down audibly and visibly before automatically dialing 911 (and your emergency contact(s)). The (probably good) assumption is that if you are aware-enough to cancel that "self-destruct" countdown, you can probably also fairly accurately assess your need for an emergency response. But if you DON'T respond, it is also damned likely that you CAN'T respond...
Our insurance company sent my wife one of those devices at no cost following her heart mitral valve replacement and hip replacement. It turned out to be touchy and temperamental. She'd just set it down on the coffee table and it would trigger dial the company. The service person had to go through a script before they'd hang up. While hanging around her neck it would swing back and forth and eventually bang against her sternum, setting it off. She averaged 3 to 5 false triggers per day. On the only day she could have used it we were walking to the stadium to watch our grandson play baseball. We went single file through a gap in the curb and I heard a thud behind me. She had fallen face first flat onto the concrete. The device didn't trigger. I drove her to the doctor and she got a 1.5" cut sewed up. Her face was black and blue for months because she was on blood thinner. We boxed the device up and sent it back. Fortunately, it didn't cost us anything.
I suspect that the Series 4 Apple Watch would behave the same way.
It's a pretty big assumption that a freebie pendant that probably cost $2 to make in China would have the same computational power to determine actual falls as the Software and Hardware inside the Apple Watch.
My wife has an Apple Watch. Its detection algorithms are extremely inconsistent: it frequently doesn't detect that she's exercising or her heart rate. It frequently doesn't detect that she has raised her wrist. Etc.
The actual title of this article should be: "Apple Watch Cannot Reliably Detect Falls." Because that's the far simpler explanation: not that it has some fancy algorithmically-generated profiles for "real falls" vs. "fake falls," but that it has one profile for "falls" that is unreliable.
You didn't say which Series your wife's Apple Watch is.
It sounds like it could detect the falls actually portrayed by Apple when recreated. Is it actually just detecting those motions and everything else is a "fake" fall? 2500 isn't very many, and it is far more credible that it is easily fooled and missing actual falls than that it is miraculous as not being tricked by fake falls.
"I somehow think it is more likely that it's not very good at recognizing serious falls in the first place."
Of course. Interesting that I had to read through almost all of the comments to get to one that points out that likely answer. -- the device, like a lot of digital stuff, just doesn't work very well. How to test?. Strap some of these things on individuals in sports where participants legitimately fall down a lot.-- American/Canadian football for example. Or put them on folks just learning to ski or ice skate.
No matter how good or bad it is, I am relatively sure that the Apple Watch's fall-detection is MUCH better than:
1. "Lifeline"-type Panic-button Pendants. Those are made for about $2, and simply don't have any real computational power.
Slashdot Mirror
I couldn't figure out why I kept accidentally opening the emoji panel, didn't think they would have done something as stupid as move it. I guess they did. Idiots. (yeah, I guess that includes me for not realizing they swapped the buttons)
At least they put it back in short-order.
Try that with Microsoft.
Considering that Apple deals with a limited number of hardware configurations, unlike Android, it surprises me when some bugs weren’t intercepted before the first release.
In theory it is best to wait a month before installing, but I admit that I installed IOS12 immediately when it came out, luckily without obvious bugs, and featuring a noticeable boost in general smoothness of operation on my 4 year old 6 Plus, good enough to make me keep my phone for another year at least.
Hello? Public Beta. Been available for MONTHS.
But that still doesn't "beat" real life conditions with hundreds of millions of users.
Anyone who has written more complicated software than "Hello World" knows that.
Always interesting how initial IOS releases always follow up with a fix release soon after. But couldn't Apple just shouldn't we expect a better product the first time? If Apple is so great, then why not polish up your first release better?
Name me ONE OS that doesn't do that.
I'll wait.
Oh, right, Android; because there just ISN'T an Update for most people.
Does it also fix the covert Chinese hardware? wouldn't want that to crash.
Moron.
That was allegedly in the SERVERS (with SuperMicro mobos) in Apple's DATACENTERS. It was NEVER in ANY Apple PRODUCT.
Besides which, Apple said it didn't actually happen (which, frankly, I am not sure if I believe).
"Other bug fixes in this update include a reorientation of the "123" number key on the iPad, which was moved in the iOS 12 update and swapped with the emoji/language key"
This drove me nuts.
At least Apple listens to feedback and actually ACTS on it, unlike, say, Microsoft, which just keeps ramming bad ideas and silly UI paradigms down everyone's throat...
Aren't they supposed to have an advantage because they have only a few models to support and tightly controlled hardware?
Considering they are currently supporting something like EIGHT generations of iPhones (from the 5s to the Xs), 4 or 5 generations of iPads (iPad mini 4 and up, IIRC), plus the 6th gen iPod Touch (which constitutes the ENTIRETY of Apple's 64-bit mobile line), all of which have differences in radio hardware, SoCs, GPUs, etc., I wouldn't say that they have to support "only a few models" anymore.
More just working, the extra care and attention apple put in really is worth the premium, right, right....right?
Sure!
Wake me when Android has zero bugs...
Idiot Haters.
It resolves an issue that could cause some iPhone XS devices not to charge when connected to a Lightning cable (...) Reports suggested multiple iOS 12 devices were affected rather than just the iPhone XS
Why phrase this in such a way? Can't you make a sentence that makes it clear from the beginning that it affects a number of iPhones and that's it?
Um, because there are iOS Devices other than iPhones...
What kind of idiot would let Tim Cocksucker run a company.
The kind that enjoys having shares in the world's first Trillion-Dollar company.
Next question?
I wish I hadn't. 12 also breaks progress syncing in iBooks with previous iOS versions, it took me a lot of digging to find that KyBook and PocketBook are the only reliable epub readers that work with older versions of iOS. Not to mention the new UI is pretty pathetic.
I actually like the new UI a bit better.
I am dissapointed in the sync not being backwards-compatible; but they have obviously changed their Library structure, and it would be inviting disaster to keep shuttling data-formats back and forth between "iBooks" and "Books" formats.
A shortage of cell towers in the mountains? Imagine that.
The issue is not the shortage of cell towers. It’s the fact that I had to restart the device every time I wanted to use it and had signal because the model would be in a bad state from the last time it lost signal and would not do anything whatsoever without a restart. That is not normal behavior. It should gracefully handle the loss and return of service without a restart.
Perhaps you should try a clean install.
https://wccftech.com/clean-ins...
Oh, and just in case they still haven't address the issue of "missing PDFs", I would suggest you save-off any PDFs you have stored in iBooks separately from your iTunes backup. Justin Case.
Better than what happened to my device, updated to 12.0, battery drained to zero, and it won't charge from anything. Apple says it's dead.
Liar.
Now it's time to upgrade from 11 to 12
I might hold off on that if I were you. I am having serious radio issues with iOS 12 and I don't know that they are fixed in 12.0.1. I have a 7 and the radios will not let me do anything unless I have at least 3 bars. Also sometimes they just stop working until I restart the device. WiFi has been flaky as well. I was in the mountains this weekend and I basically had to restart my phone every time I wanted to use it. It seems the current radio firmware does not like when you have low reception.
So, you are recommending NOT upgrading to an OS version that announces fixes for some radio issues?
Talk about useless advice!
If only your manners could make up for your nauseating love of apple and blind hatred of real tech companies
If you think Apple doesn't qualify as a "real tech company", then it is YOU that needs some attitude-adjustment.
I've got a sledgehammer. Perhaps you should borrow it and attend some "Hitting yourself over the head" Classes at the Argument Clinic.
And talk about "Nauseating": Your blind HATRED of all things Apple, because... Apple, is misplaced, immature, AND Nauseating.
And good manners NEVER go out of style.
Wanna borrow that sledgehammer, or should I bring it to you?
LOL what a fucking IDIOT
SO buggy code that apple fixed DOESNT count as a bug.
WFT kind of STUPID BLIND apple WORSHIPPER logic if that?
You are a disgrace
Sure.
Now, let's go back to Linux 0.09 and start adding up the bugs, shall we? Because that is EXACTLY the "standard" you are attempting to apply to WatchOS.
And no, bugs in code that are FIXED are NO LONGER COUNT AS BUGS.
Or has Linux been 100% bug-free since it was first foisted upon an unsuspecting world?
Moron.
Over a year ago (don't recall exactly when, the book was published last December) I used a similar device in The Eridani Convergence when the protagonist hurls himself from a moving car (autonomous, and it had been hacked to kidnap him) in the middle of nowhere. He wakes up in a hospital room:
I like to think that someone at Apple read that and thought it was a good idea, but probably they were already working on it. Or they worked fast. ;)
I can beat that by about 5 years.
In fact, when the iPhone first started having 3-axis Accelerometers, I considered making an "Emergency Call" App with built-in Fall-Detection.
Unfortunately, at the time (and maybe still), Apple prohibited that type of App from being published in the App Store.
But in this case, this instrinsic feature of WatchOS 5 is a obviously a LOT deeper-integration than a simple App can attain, even without the App Store restrictions. So it's an entirely different case.
Sounds like they trained a neural network on a lot of falls.
Which means, they don't really know what they actually trained it to do either.
Just because that's the way YOU would approach the problem, is not any assurance that Apple took JUST that approach.
Well, that proves it. Time to put it on over a million people's wrists without worrying about any false callouts.
The likelihood of significantly high numbers of truly false "Callouts" is drastically reduced by the fact that the Watch counts-down audibly and visibly before automatically dialing 911 (and your emergency contact(s)). The (probably good) assumption is that if you are aware-enough to cancel that "self-destruct" countdown, you can probably also fairly accurately assess your need for an emergency response. But if you DON'T respond, it is also damned likely that you CAN'T respond...
Bracing for the fall is actually one of the worse things you can do.
True.
But without specific training/practice, it is a nearly involuntary action.
I have to tell my watch how fucking old I am now? What else does it need to know?
No, Hater.
When you sign up for an AppleID, IIRC, DOB is part of the required information. I would assume it uses that.
es, I know the watch asks you if you are ok before calling but you might be distracted long enough to not notice or be able to respond.
If you are not responding to an audible countdown and message then there is likely something wrong, and it SHOULD call.
Our insurance company sent my wife one of those devices at no cost following her heart mitral valve replacement and hip replacement. It turned out to be touchy and temperamental. She'd just set it down on the coffee table and it would trigger dial the company. The service person had to go through a script before they'd hang up. While hanging around her neck it would swing back and forth and eventually bang against her sternum, setting it off. She averaged 3 to 5 false triggers per day. On the only day she could have used it we were walking to the stadium to watch our grandson play baseball. We went single file through a gap in the curb and I heard a thud behind me. She had fallen face first flat onto the concrete. The device didn't trigger. I drove her to the doctor and she got a 1.5" cut sewed up. Her face was black and blue for months because she was on blood thinner. We boxed the device up and sent it back. Fortunately, it didn't cost us anything.
I suspect that the Series 4 Apple Watch would behave the same way.
It's a pretty big assumption that a freebie pendant that probably cost $2 to make in China would have the same computational power to determine actual falls as the Software and Hardware inside the Apple Watch.
Okay, this is a bunch of bullshit.
My wife has an Apple Watch. Its detection algorithms are extremely inconsistent: it frequently doesn't detect that she's exercising or her heart rate. It frequently doesn't detect that she has raised her wrist. Etc.
The actual title of this article should be: "Apple Watch Cannot Reliably Detect Falls." Because that's the far simpler explanation: not that it has some fancy algorithmically-generated profiles for "real falls" vs. "fake falls," but that it has one profile for "falls" that is unreliable.
You didn't say which Series your wife's Apple Watch is.
It sounds like it could detect the falls actually portrayed by Apple when recreated. Is it actually just detecting those motions and everything else is a "fake" fall? 2500 isn't very many, and it is far more credible that it is easily fooled and missing actual falls than that it is miraculous as not being tricked by fake falls.
You forgot to say "In my not so humble opinion".
"I somehow think it is more likely that it's not very good at recognizing serious falls in the first place."
Of course. Interesting that I had to read through almost all of the comments to get to one that points out that likely answer. -- the device, like a lot of digital stuff, just doesn't work very well. How to test?. Strap some of these things on individuals in sports where participants legitimately fall down a lot.-- American/Canadian football for example. Or put them on folks just learning to ski or ice skate.
No matter how good or bad it is, I am relatively sure that the Apple Watch's fall-detection is MUCH better than:
1. "Lifeline"-type Panic-button Pendants. Those are made for about $2, and simply don't have any real computational power.
2. Nothing. Which is what most people have...