Organized an event last week, Apple presented its new smart devices and operating systems to users. Those who use fake AirPods, which are called fake AirPods, will have problems with the iOS 16 update.
Chinese companies had discovered a vulnerability that would allow the fake Apple accessories they produced to be detected as genuine by the iOS operating system. Counterfeit AirPods, which have been on the market for a while, can now be detected by iPhone and iPad.
Fake AirPods warning for those who update iOS 16
Emphasizing customizability in the new version, Apple made significant changes to the lock screen with iOS 16. The lock screen, which has become fully customizable, has managed to win the appreciation of users.
Social networking functionality has been added next to frequently used items such as emoji and gifs in the iMessage app. Especially for the iMessage application, which has a very high usage rate in the USA, there are also features to edit and undo the sent message.
Apple, with the precaution it takes for non-original Lightning cables, displays “this accessory is not supported” warning on the screen. The company, which has developed a similar security measure for other counterfeit accessories, will display the warning text “AirPods cannot be verified” on the screen.
Below the warning text are the options to Connect and Connect in Bluetooth Settings. Users who want to connect fake AirPods to their device will only be able to do this from the Bluetooth Settings menu.
Some companies are known to sell fake AirPods under the original name. With this development, fake accessory scams are expected to drop drastically.
iPhone models that will receive the iOS 16 update:
- iPhone 13 mini, iPhone 13, iPhone 13 Pro, iPhone 13 Pro Max
- iPhone 12 mini, iPhone 12, iPhone 12 Pro, iPhone 12 Pro Max
- iPhone 11, iPhone 11 Pro, iPhone 11 Pro Max
- iPhone Xr, iPhone Xs, iPhone Xs Max
- iPhone X
- iPhone 8, iPhone 8 Plus
- iPhone SE, iPhone SE (2022)
What do you think about this subject? You can share your ideas in the comments section and on the SDN Forum.
18516
