Battery problems? Like what? My 14 PM gets more than 2 days of regular use on a charge.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Investigating Apple Watch Series 8 and Ultra Microphone Issues
- Thread starter MacRumors
- Start date
- Sort by reaction score
Battery problems? Like what? My 14 PM gets more than 2 days of regular use on a charge.
My AW7 showed the microphone with the line through it both with and without a white background giving me the idea that BOTH were saying that the mic was disabled. The one without the white background (I think) seemed to work. The slash through the mic did not change, just the background.
Obviously a UI flaw.
The slash through something usually means it's disabled, or not usable (noop), so why it stayed on the icon was unfortunate. It obviously needs some tweaking...
Obviously a UI flaw.
The slash through something usually means it's disabled, or not usable (noop), so why it stayed on the icon was unfortunate. It obviously needs some tweaking...
AND the iPad Mini 6!! It lasts days after charging, and I'm not touching it at all, while it just runs from 100% to 3% yesterday.
And, APPLE!!! Please fix the 'screen light to 1000 lumens' problem! Plugging it in shouldn't be a blinding experience. Yikes...
(Since people are complaining about unrelated battery issues)
Yup, will be a long time until my 13 PM and Series 7 AW leave my possession.
Apple is mired in QC issues and increased component cost cutting.
I live a very active lifestyle & still use my Apple Watch 6. The battery is fine. It’s rugged enough & does everything I need. I won’t be upgrading for awhile. 😉
Last edited:
Don't expect Matter to be a silver bullet. While I'm excited about the expansion of possible gear to use in my HomeKit environment, Matter has taken a long time to come out and we should expect further bugs and incompatibilities. Not all vendors support Matter, either, and there are whole classes of devices still not covered by the protocol. I still can't believe Matter doesn't include cameras.
I found a strange bug on my Noise app. It tells me noise reduced by my AirPods, which wouldn't sound unusual except that I wasn't wearing any AirPods. At the very bottom it shows what the noise level would be if I weren't wearing AirPods, and the numbers are basically the same, so the bug is that it mentions AirPods at all.
I'd say everyone is terrible at programming. Ever since CPU designers started promoting multi-threaded programming because they couldn't just increase the clock speed anymore, programming has gone downhill. I suppose that's human because people are fallible. Back in the old days, multi-threading was considered a no-no because it complicated programs and made bugs far more likely. When things are serialized, it's a lot easier to write bug-free code. With multiple things happening simultaneously on different threads, it's not so easy. But with CPU design the way it is now, you're forced to do it to get maximum performance. That leads to bugs because we simply cannot anticipate what happens on other threads that can mess up what we're doing.
I do not exempt myself from being fallible, but as a 30 year veteran of programming, I can say that every reasonably complex program has thousands of bugs that go unfixed. On my last major project, there were over 2,000 bugs in our bug database that were marked as medium to low priority (some of them with high severity) and labeled as never to be fixed because it humanly isn't possible to make bug free code in any large, complex program. QA is similarly handicapped by what scenarios they can imagine. They write their test plans according to whatever scenarios and conditions they can imagine and test for those, but no one can anticipate everything. A bug that happens frequently is one that's easily found and fixed. A bug that happens to a few thousand people out of millions of devices is a lot harder to find because it's pure luck if your testing finds the bug.
I'll give you an example of a bug that actually crippled our software and went unfound for years. I won't mention which company I worked for, but I've never worked for Apple or anyone associated with them. We had a server product that underwent an upgrade starting at 11pm and downtime was expected to be no more than a couple of hours. The server refused to run properly after the update was applied. It would start up and shut down a few seconds later. Eight hours later, we still couldn't figure it out and backed out our changes, losing customer data. The prior code still wouldn't start. A few hours later, we discovered the problem was a timestamp for a single record that was in the future. Somehow, a record slipped into the database with a future date. We never did figure out how it happened, but the upgrade was not the cause. Some error checking in our start up code saw the errant date and aborted the start up. The server would have continued running merrily as long as we didn't shut it down, but when it did get shut down for the update, the bug was exposed. The bug had been there from the beginning years ago, but never showed itself until that one instance when a bad date was entered a few weeks before the upgrade. We lost a lot of customer data and had a lot of very angry customers over that. Customer support had to manually rebuild records over several weeks. This instance illustrates just how hard it can be to anticipate every problem. No one ever envisioned a future date slipping into the database because the date was automatically filled out via GPS. Out of millions of records, it took one to cripple the server. We deleted the one record and the server started right up. We patched the code that night to check for a future date. That was one of the worst nights of my career.
When I see bugs like this get reported, and it doesn't matter who it is, I just shake my head and commiserate with the programmers who work hard but are human in the end. Sure it's bad when a major bug shows up. There are no excuses because customers are entitled to be angry at flaws in products where they spend their hard-earned money. Perhaps changes can be made in procedure to make it easier to find those bugs. But as programs become more and more complicated and features are piled upon features, bugs are inevitable. They could be due to incompetence, but there will always be bugs that are simply unavoidable. I'm writing this just to give people a window into the world of programmers.
I disabled Siri ‘raise to speak’ and Hé Siri on my Ultra restarted and problem is gone ever since (1 week now). Don’t know which of the 2 settings causes the problem…
I have this exact bug on my Apple Watch SE (1st generation). I thought I was going crazy with the phone reporting it was in water lock mode and disabling the microphone. Luckily pulling up the quick shortcuts menu by swiping up resets the microphone again.
Most definitely.
I know Siri on the HomePod cannot understand half of the requests. You tell it to play a song — it plays a remix of that song. I was listening to that new Beyoncé album the other day and I told it to play “CUFF IT” and Siri always calls it “CUFF I.T.”
More of that high-quality work-from-home bugs coming through....
Can we just cut it out with the anti-WFH in every....single....post please? There is ZERO proof of this. Apple has had big BIG issues in the past back when even the "perfect" Steve Jobs was around. I am getting tired of this site and the 20-50 posts saying "THIS IS ALL WFH!!!!!!"
And you actually aren't saying what you think you are saying. Your complaints lead to bad management. If poor performing people are still employed, that is a bad management structure. NOT work from home inherently being bad. Fire the poor performers and hire replacements that thrive on WFH. Things have changed. WFH is a major MAJOR MAJOR bonus to ANY job these days. Sometimes more of a killer benefit that higher pay. I am able to work for any company in the US now which is great.
And lastly, back in 2015, I applied for Apple. Back then they had remote work. This isn't anything new. Lots of places also have programmers off in India.
And you actually aren't saying what you think you are saying. Your complaints lead to bad management. If poor performing people are still employed, that is a bad management structure. NOT work from home inherently being bad. Fire the poor performers and hire replacements that thrive on WFH. Things have changed. WFH is a major MAJOR MAJOR bonus to ANY job these days. Sometimes more of a killer benefit that higher pay. I am able to work for any company in the US now which is great.
And lastly, back in 2015, I applied for Apple. Back then they had remote work. This isn't anything new. Lots of places also have programmers off in India.
Last edited:
Life in a nutshell. I’m guessing the pandemic is partially or fully responsible in one way or another, both here and in China. Maybe staffing issues and inadequate testing?
My S8 mic wasn't working at all (phone calls, Siri, noise app) and I did these two things and FIXED IT instantly, didn't even restart. Thank you very much! Definitely, some bug with Siri in watchOS 9, which I'm sure will be fixed but incredibly frustrating considering I have a brand new watch.
Yep, just got mine today, don't buy one until it's fixed, returning mine, dicked with it from 10 AM until now, bummer though, I gave my perfectly fine 4 to a friend when I got this heap o' dung. Voice memo "Tap to record " does nothing, no reaction then when it did work only rice crispies came out of the speaker. "Hey Siri" makes it freeze up and I have to turn it off and back on.
Last edited:
so three weeks into my ultra mic not working, sent in for service, three hours of phone called and 3 genius visits in which they finally tell me Apple has a sent a memo not to send in the watches for repair and customers should wait for a software fix. On the phone with apple care, she told me she was blocked from replacing my watch and was told to tell the customer to wait for a software fix
I figured out how to reliably reproduce this issue on my Series 9 GPS + iPhone 12 Mini
- Add the large noise complication to a watch face. It should always show real time measurement bars when the watch is awake
- Restart the watch (to make sure the noise complication is working… when it stops working, the only way to restore function is a restart)
- Have someone call you and answer the phone call on the watch
- during the call, bring up the keypad and tap some numbers randomly
- Hang up the call and put the watch face to sleep
- Wake up the watch. The noise complication should show the measurement bars for a second and then it will grey out and say “measurement suspended”