Let’s play iPhone defect excuse bingo:
- it’s just indexing data it will be ok after a week/month.
Let’s play iPhone defect excuse bingo:
- it’s just indexing data it will be ok after a week/month.
Not trying to excuse anything here, if you can provide a reason to believe it's not caused by those background processes I'm completely fine with the explanation that iOS is just buggy or the hardware has heat issues. Frankly the behavior does sound pretty bad even if it's "just" the photo analysis thing, the obvious solution would be to 1) make the analysis sync with the photos, and 2) make the background processing slow enough to not notably increase heat/decrease battery life, and 3) have a place in the OS where you can see the progress and tell it to go as fast as possible. Their philosophy of hiding everything from the user doesn't seem to be working well here.
As a software developer I find it easy to come up with good explanations for things like these, but as an end user, I don't care. My photos are searchable but I don't think I've ever used that feature, I wouldn't want my phone to get hot and waste battery life indexing a picture of a funny tree I took five years ago. Do that stuff while charging overnight, and keep thermals under control while you do it. You don't need a fancy neural processor to detect that I leave my device plugged in at 100% every night, maybe make use of that obvious excess of downtime and processing power.
Edit: Battery efficiency says it's at 87%... feels about 80 though /shrug.
Which is to say it’s not unimaginable that photo indexing is part of it.
Someone spending $1000-2000 doesn’t want a hot draining phone just so they can search “dog” in their photo album on day 1 or 2.
They should throttle it - much better to tell the user the feature isn’t ready yet or something. Or you know, give the user the choice of running that feature fast or slow - but that would be anathema to Apple.
Ps I am an Apple fan boi. Own lots of Apple devices