Yeah I was gonna post something along the same lines. Really rock solid.
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.
iOS 15.5 Beta 2 ― Bug Fixes, Changes, and Improvements
- Thread starter Banglazed
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Yeah I was gonna post something along the same lines. Really rock solid.
This seems new in the Weather app, crowdsourcing conditions:
I have the option on 14.4.1 as well. This box is just smaller and not as big as on 15.5 beta 2This seems new in the Weather app, crowdsourcing conditions:
Usually this error comes from 1 of 3 things:
- iPhone locked with passcode (try to unlock it before starting the whole procedure)
- outdated iTunes (check for updates)
- some antivirus or firewall software is interfering with iTunes (try to disable them)
It was discussed in another thread, the latest version of itunes seems broken in this regard, I had to download the previous version to make it work without problems. Maybe iMazing uses some updated itunes component to restore and the bug is replicated.
@OhMyMy
Summary of OTA vs IPSW (update method)
After two weeks of chatting to Craig, he only offered a fix for a buggy OTA install, then I was passed onto a Senior tech advisor who dodged answering my question in a similar fashion with chuckles like “that’s why we have the IPSW method at hand” His soul purpose was just to make sure I was ok and my phone was running smoothly, to be honest.
Tech support said that “every reported bug gets read by a human and then cataloged. Please don’t stop reporting bugs they are really valuable to Apple” after questioning bug reporting quite hard at Apple, and then he went.
No answer or explanation apart from they are both binary identical, to why we see bugs from OTA updates vs IPSW tethered method. Just that ultimately, the IPSW file will potentially fix any issues you might of had prior to an OTA update. That’s all they seemed happy with, on the surface.
Yes I know what you’ll say, things werent carried out in a controlled environment, you didn’t run enough test on devices, you can’t reinstall using OTA anyway (thanks for pointing that one out last time, I didn’t know that ?) but, to see the issue at hand enough to report to Craig from real world, the developers, designers and Apple fans in the group that tested this theory saw it for themselves. That was enough for us to carry on. And before you think this is me blowing any big horns here, it’s not, this has been done with no ego, but what started out as an observation and then actually a real provable thing, got me interested and was fun but unfortunately I can’t come to the table with a definitive answer just that the consensus is from Craig and Tech support, “if something is wrong with your phone, do an IPSW file reinstall or restore”
So I take from that, we’ll conclude in my head, why risk there being anything wrong in the first place using OTA! Just update using tethered IPSW file, which will decrease your bug output - as found in research and testing and ultimately what Craig suggested to do anyway if you have bugs.
Just for those of you that have “never had an issue with OTA” have you ever tested that claim, by finding a few new bugs with a build, then reinstalled using the IPSW file and check some of those bugs have gone? To actually test you didn’t have any issues with the OTA? Otherwise, just having a successful instal doesn’t class as never having an issue with it. If the bug/s are still there, your OTA was good, if some have been fixed, as we saw, that’s my point. IPSW file method is kinda king ?
Summary of OTA vs IPSW (update method)
After two weeks of chatting to Craig, he only offered a fix for a buggy OTA install, then I was passed onto a Senior tech advisor who dodged answering my question in a similar fashion with chuckles like “that’s why we have the IPSW method at hand” His soul purpose was just to make sure I was ok and my phone was running smoothly, to be honest.
Tech support said that “every reported bug gets read by a human and then cataloged. Please don’t stop reporting bugs they are really valuable to Apple” after questioning bug reporting quite hard at Apple, and then he went.
No answer or explanation apart from they are both binary identical, to why we see bugs from OTA updates vs IPSW tethered method. Just that ultimately, the IPSW file will potentially fix any issues you might of had prior to an OTA update. That’s all they seemed happy with, on the surface.
Yes I know what you’ll say, things werent carried out in a controlled environment, you didn’t run enough test on devices, you can’t reinstall using OTA anyway (thanks for pointing that one out last time, I didn’t know that ?) but, to see the issue at hand enough to report to Craig from real world, the developers, designers and Apple fans in the group that tested this theory saw it for themselves. That was enough for us to carry on. And before you think this is me blowing any big horns here, it’s not, this has been done with no ego, but what started out as an observation and then actually a real provable thing, got me interested and was fun but unfortunately I can’t come to the table with a definitive answer just that the consensus is from Craig and Tech support, “if something is wrong with your phone, do an IPSW file reinstall or restore”
So I take from that, we’ll conclude in my head, why risk there being anything wrong in the first place using OTA! Just update using tethered IPSW file, which will decrease your bug output - as found in research and testing and ultimately what Craig suggested to do anyway if you have bugs.
Just for those of you that have “never had an issue with OTA” have you ever tested that claim, by finding a few new bugs with a build, then reinstalled using the IPSW file and check some of those bugs have gone? To actually test you didn’t have any issues with the OTA? Otherwise, just having a successful instal doesn’t class as never having an issue with it. If the bug/s are still there, your OTA was good, if some have been fixed, as we saw, that’s my point. IPSW file method is kinda king ?
I think you need 2 things to prove your theory to Craig and company. A video showing the issue repeated exactly the same way for the OTA and IPSW showing that the bug exists with the OTA and not with the IPSW. Along with a sysdignose file. Provide video proof that is what I do when I send an issue to Craig.
Wasn’t even asked for. So you could read into that one of two ways:
1. They are aware of something.
2. They aren’t actually that bothered as they presented a fix.
Or 3. What’s this raving idiot banging on about.
Way back in the dark ages when an iTunes update was the only method I either had the same number of issues or perhaps even more, hard to remember back that far. I do remember once foolishly following someone’s suggestion to wipe the phone and re-install for an issue I was convinced was an ios bug not an issue with my phone or method of software update. Of course after doing so the bug remained until the next release fixed it. So I’ve never done that since. And now with the seamless update method OTA there has never been a reason to consider doing so. If my phone were not functional - a serious issue - my first move, probably, would be to get an appointment at an Apple Store where they probably would complete such a process, or give me a new phone
Since those dark days I don’t think there’s been a non-ios related bug on my devices other than certain issues related to specific iCloud accounts such as the disappearance of Frequent sites in Safari. I know people who still have those on their devices and people like me and others here who don’t. And obviously if you have a serious problem with a device not functioning, overheating, battery plummeting for no reason a software release on top of such a device likely won’t fix anything. Although it seems the battery thing seems to have been resolved for some here with an update. And I do have to admit that I had two phones replaced - a 6S and a 7 - because of swollen batteries. But ironically they both functioned properly with no issue other than the batteries had popped the cases. I don’t think an IPSW would have fixed either.
I was just trying to point out that when you encounter an issue it is best to have a record showing the issue and how it manifests itself. Steps to repeat are important to help triage an issue. Simply trying to explain the issue can lead to misunderstanding what is meant. It is so easy to misunderstand or interpret the meaning of what is written. Having a video to show the problem is the best thing and it will show time stamps to correlate to the sysdiagnose file.
So I didn't mention any recordings or videos, does that mean I don't have them???
You cant write every little thing down on here, to cover every single little tiny base, so someone cant find something to pick you up on.
Start of my original message says Summary.
Attachments
My theory is, and after seeing how other manufacturers like Samsung, for example, perform OTA updates, it is that Apple performs part of the hot patching, that is, with the system turned on. While in Samsung it extracts the firmware, and reboots to patch the system, in Apple it seems that part of this is done while extracting the system, hence an increase in System in the storage section. Then it restarts to finish installing the rest, like the modem and others. Of course I'm not sure if this is the case, but the behavior of the system leads me in this direction, besides that it can explain this randomness of strange errors that sometimes happen. When you update with ipsw, all the patching is done off, and there you can see that it is almost free of errors, apart from those that the iOS version in question might have.
It does really fascinate me how being told two forms of updating are identical and should have the same outcome, but proven time and time again, this is not the case. It’s not about me being right, that couldn’t be further from the truth, I was just after an explanation of something I found out. The differences are there and the results are for the better in quality of a product for people.
There has to be a slight difference, or sequence of something running between the two forms of updating, and that small change can have an effect on the quality of the update to your device. Interesting theory, it’s something like this I was expecting when being told about OTA or IPSW tethered updating. Thanks ??
Last edited:
Been doing a bit of playing around with the Camera (13PM).
Didn’t see any changes noted however I am finding it more difficult to get great macro shots on B2.
The Camera is seriously over-sharpening on some, over-softening on others.
Here are some examples taken in bright light (outdoor)
Taken on the front porch using a tripod.
Didn’t see any changes noted however I am finding it more difficult to get great macro shots on B2.
The Camera is seriously over-sharpening on some, over-softening on others.
Here are some examples taken in bright light (outdoor)
Taken on the front porch using a tripod.
Attachments
Way back in the dark ages when an iTunes update was the only method I either had the same number of issues or perhaps even more, hard to remember back that far. I do remember once foolishly following someone’s suggestion to wipe the phone and re-install for an issue I was convinced was an ios bug not an issue with my phone or method of software update. Of course after doing so the bug remained until the next release fixed it. So I’ve never done that since. And now with the seamless update method OTA there has never been a reason to consider doing so. If my phone were not functional - a serious issue - my first move, probably, would be to get an appointment at an Apple Store where they probably would complete such a process, or give me a new phone
Since those dark days I don’t think there’s been a non-ios related bug on my devices other than certain issues related to specific iCloud accounts such as the disappearance of Frequent sites in Safari. I know people who still have those on their devices and people like me and others here who don’t. And obviously if you have a serious problem with a device not functioning, overheating, battery plummeting for no reason a software release on top of such a device likely won’t fix anything. Although it seems the battery thing seems to have been resolved for some here with an update. And I do have to admit that I had two phones replaced - a 6S and a 7 - because of swollen batteries. But ironically they both functioned properly with no issue other than the batteries had popped the cases. I don’t think an IPSW would have fixed either.
A lots changed since those days and even Craig Federighi suggest a reinstall/restore - can understand why you wouldn’t listen to people on here after that. That’s totally your call. You might be missing a trick there though.
Were on beta software after all and if things get that serious, after some house keeping yourselves, and then some time on an official build, then it’s a trip to the store last resort totally. I don’t think anyone on here thinks IPSW file will fix everything, just reduce some small bugs and leave behind the ones that Apple are working on fixing, could be a way of looking at it.
And it certainly won’t sort out hardware failures which you sound like you're describing.
Last edited:
They have a very shallow depth-of-field, which is to be expected especially if it's not very bright.
Could be that it's not focussing on the right area.
Could be however the light was direct early afternoon sunlight.
For focus help, I do use the grid. Would luv a focus point like Halide uses.
Still, this was not the result I was hoping for nor expecting.
@adrianlondon
Did a round 2 of macro type photos - 13PM.
Afternoon direct sun. Camera and Halide.
One item of note - Halide has a smaller subject photo from the same distance.
Just for comparison.
Camera followed by Halide - 3 sets.
Did a round 2 of macro type photos - 13PM.
Afternoon direct sun. Camera and Halide.
One item of note - Halide has a smaller subject photo from the same distance.
Just for comparison.
Camera followed by Halide - 3 sets.
For me camera wins in sets 2 & 3. Also a debate as to the H, even if that is classed as macro it’s so far away.
But the camera blows out on the pink flower. Not holding half as much detail in shadows - Needs more contrast as it look quite flat in comparison. And struggling with focus a little.
Yeah, time permitting I am going to play around a bit this afternoon.
See what I come out with.
Are these actually "macro" shots? They look kinda far away from the subject. I know you can technically trigger the macro mode from a little bit of a distance but I wonder if when you do, does the camera flicker back and forth between true macro and just using the telephoto lens?
These were taken at a range 1"-2".
Camera has a dedicated Macro icon while Halide does not.
I had that same thought. Typically it’s 1:1 or greater. I’m finding that macro mode doesn’t activate on my 13PM until I am within 6” of the subject.