fh9302

This implies 30% less power at matching peak performance, not faster performance like the title says.

Mishaal Rahman claims it's purely a business decision and not an artifical limitation set by Qualcomm: https://twitter.com/MishaalRahman/status/1710442249778086260

Can you show me evidence that Qualcomm refuses to support chipsets even in the case where they would get paid to extend support?

If that's the case, why do phones with the Tensor G1 and G2 only receive 3 major updates? That even applies to the Pixel Fold, a $1800 phone released a couple months ago. There's no Qualcomm to blame here, it appears to be purely a business decision by Google.

There was no compatibility problem, Google intentionally blocked the installation to avoid reviewers testing the chip. The benchmarks worked without issues when sideloaded, but not every reviewer bothered to do that.

Not sure if this is really surprising. Apple released the M2 in the begining of Q3 2022, but in Q3 2023 they did not release any new Mac chip. I expect a significant YoY decline in this case.

The M3 will likely be based on the A17, while the M2 was based on the A15. That will be a more significant jump compared to M1 to M2.

It's similar to screen sharing over FaceTime. You first have to accept it, afterwards the technician can see a video stream of your phone and tell you where you have to click. They can't directly interact with your phone.

Third-party passkey providers got added with iOS 17. I don't know which apps apart from 1Password support it yet but the API is there.

Third-party passkey providers got added with iOS 17.

https://www.corbado.com/blog/apple-passkeys-integration

On iOS you can use third party software to manage passkeys, there is no inherent cloud requirement.

Can you link to some evidence that these cryptocurrency thefts are related to zero-click attacks on iOS?

The LastPass breach resulted in theft: https://www.theverge.com/2023/9/7/23862658/lastpass-security...

The iPhone 7S does not exist. You have linked to a pre-release rumour article for a non-existent device.

Are you using the Instagram app? It is documented that a bug in the app in combination with iOS 17 causes phones to massively heat up while doing basically nothing.

https://www.youtube.com/watch?v=P6X2ZIkYFsQ

GSMArena bought two iPhone 15 Pro Max from different retailers to test the overheating issue and they were unable to replicate it.

> Lastly, we did read reports of overheating iPhones, some during fast charging. For this review, we used two iPhone 15 Pro Max units, obtained from different retailers, and neither of those became unbearably hot even after an hour of GPU stress testing. Warm, rather unpleasantly (but not concerningly) - sure, but hot - never. We know people have experienced and documented such issues, but we haven't been able to replicate those so far on our units.

They think it's a bug in iOS 17 that causes some phones to overheat.

> And since we ran the same tests on the iPhone 14 Pro Max, which last year we crowned as a phone with excellent stability, we were surprised to see that now, under iOS 17, its stability has gotten worse. That's why we think there is some software issue at play in addition to/or just contributing to the poor heat dissipation.

https://www.gsmarena.com/apple_iphone_15_pro_max-review-2618...

Google refuses to open up the Android RCS API to third party developers. To me this seems like an attempt to lock in users into their own messaging app, unlike SMS which does support third party apps like Textra.

https://twitter.com/TextraSMS/status/1568128147044057088

For those curious, yes Apple did fix the Sonoma firewall bug reported by Mullvad.

https://mullvad.net/en/blog/2023/9/22/macos-14-sonoma-firewa...

Ignore my previous comment, the wording on the website was a bit ambiguous and I misinterpreted it.

According to your own link file names in iCloud Drive are E2EE.

You can find some more information here: https://www.reddit.com/r/apple/comments/5mnpt2/comment/dc5n4...

It's similar to FaceTime screen sharing, the support employee can only see a video feed of your screen but can't directly interact with it.

https://support.apple.com/en-us/HT212734

It's purely a video feed similar, it doesn't give the support employee direct access to the device. It's similar to screen sharing with FaceTime: https://support.apple.com/en-us/HT212734

How is manually turning on iCloud E2EE different to manually searching a provider that supports E2EE by default? This isn't like messaging where the other person also needs E2EE enabled.

The article doesn't mention it but Lockdown Mode on iOS blocked this exploit chain.

Apple pays up to $2M for such zero click exploits.

Lina received a $150k bounty for this exploit.

Autocorrect doesn't suggest whole sentences so it is irrelevant if the remaining sentence is gibberish or not.

They warned Apple based on rumours but that doesn't prove that MFi certification for USB-C ever existed.

The iPhone 15 supports Qi2, which is based on Apple's MagSafe standard. It's not proprietary.

It's the same vulnerability as in the article, PWNYOURHOME would have been avoided with lockdown mode.

> Researchers believe Timchenko’s hackers used the so-called “PWNYOURHOME” vulnerability

The phone was not in lockdown mode as it would have prevented the attack.

https://citizenlab.ca/2023/09/blastpass-nso-group-iphone-zer...

> We believe, and Apple’s Security Engineering and Architecture team has confirmed to us, that Lockdown Mode blocks this particular attack.

https://citizenlab.ca/2023/04/nso-groups-pegasus-spyware-ret...

> For a brief period, targets that had enabled iOS 16’s Lockdown Mode feature received real-time warnings when PWNYOURHOME exploitation was attempted against their devices. Although NSO Group may have later devised a workaround for this real-time warning, we have not seen PWNYOURHOME successfully used against any devices on which Lockdown Mode is enabled.